For example, you want to set 40% alpha transparence to #000000
(black color), you need to add 66
like this #66000000
.
Discover gists
hdmi_group=2 | |
hdmi_mode=87 | |
hdmi_cvt=2560 1440 60 3 0 0 1 | |
max_framebuffer_width=2560 | |
max_framebuffer_height=1440 | |
hdmi_pixel_freq_limit=400000000 |
use std::fmt::{ Debug, Display, Formatter, Result }; | |
use std::string::ToString; | |
#[derive(Debug)] | |
struct Slice<'a, T: 'a> { | |
data: &'a [T] | |
} | |
impl <'a, T: ToString> Display for Slice<'a, T> { | |
fn fmt(&self, f: &mut Formatter) -> Result { |
<!DOCTYPE html> | |
<html lang="en"> | |
<head> | |
<meta charset="UTF-8" /> | |
<meta name="viewport" content="width=device-width, initial-scale=1.0" /> | |
<title>Document</title> | |
<style> | |
section { | |
background-color: #80b8e9; |
#/usr/bin/env sh | |
curl --proxy http://127.0.0.1:8080/ --user-agent burl --insecure "$@" |
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore
is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules
directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
- Create a file called
.gitignore
in your home directory and add any filepath patterns you want to ignore. - Tell git where your global gitignore file is.
Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignore
for.gitignore
in your home directory, if you prefer.
ZigZag-Encoding | |
--------------- | |
Maps negative values to positive values while going back and | |
forth (0 = 0, -1 = 1, 1 = 2, -2 = 3, 2 = 4, -3 = 5, 3 = 6 ...) | |
(i >> bitlength-1) ^ (i << 1) | |
with "i" being the number to be encoded, "^" being | |
XOR-operation and ">>" would be arithemtic shifting-operation |
Learning Rust
The following is a list of resources for learning Rust as well as tips and tricks for learning the language faster.
Warning
Rust is not C or C++ so the way your accustomed to do things in those languages might not work in Rust. The best way to learn Rust is to embrace its best practices and see where that takes you.
The generally recommended path is to start by reading the books, and doing small coding exercises until the rules around borrow checking become intuitive. Once this happens, then you can expand to more real world projects. If you find yourself struggling hard with the borrow checker, seek help. It very well could be that you're trying to solve your problem in a way that goes against how Rust wants you to work.
(updated June 2024)
The APs in this list are ordered from highest to lowest performance. However, unless you have an insane amount of devices you likely do NOT need to buy the most expensive, highest performance AP. You can also check Ebay for deals, especially on older equipment. In terms of best price-to-performance, the U6 Pro/Mesh/InWall series is the sweet spot in my opinion and is the best choice for most deployments.
All APs in this list support both wired backhaul and mesh modes. However, wired connections are strongly recommended for better performance and reliability.
Number of spatial streams are listed in order of 2.4GHz, 5GHz, 6GHz.
# When using the Repository Template feature on GitHub, it does not follow the same rules as Composer create-project or ZIP downloads. | |
# For this reason, we have this script which will configure the repository the first time it is set up in order to normalize it. | |
name: Configure template repository | |
on: | |
# Run when branch is created (when the repository is generated from the template) | |
create: | |
# Only keep latest run of this workflow and cancel any previous runs | |
concurrency: |