#GNU Screen Cheat Sheet
##Basics
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| L1 cache reference 0.5 ns | |
| Branch mispredict 5 ns | |
| L2 cache reference 7 ns 14x L1 cache | |
| Mutex lock/unlock 25 ns | |
| Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
| Compress 1K bytes with Zippy 3,000 ns 3 us | |
| Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
| Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs
| # terminfo and termcap for nice 256 color terminal | |
| # allow bold colors - necessary for some reason | |
| attrcolor b ".I" | |
| # tell screen how to set colors. AB = background, AF=foreground | |
| termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm' | |
| # erase background with current bg color | |
| defbce "on" |
These rules are adopted from the AngularJS commit conventions.
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message consists of a header, a body, and a footer.
| // This requires a google developers console project. That UI changes regularly and I found it hard to learn, but at the time I'm creating this, the steps are: | |
| // - At the top-right, select or create a new project (can't give step-by-step details here) | |
| // - Visit https://console.developers.google.com/apis/api/drive/overview | |
| // - Enable API with your options (not sure they matter much, but API must be enabled) | |
| // - Visit https://console.developers.google.com/permissions/serviceaccounts | |
| // - Create a new service account if you don't already have one or don't have one you want to use for these API calls. Select the "Furnish new private key" option and the JSON format along with "Enable Google Apps Domain-wide Delegation". | |
| // - Save provided JSON in a SECURE location (don't include in your source code and ensure it's ignored by GIT) | |
| // You can generate new keys and/or revoke this one at https://console.developers.google.com/apis/credentials | |
At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.
git commit --amendThis will open your $EDITOR and let you change the message. Continue with your usual git push origin master.
(NOTE: Current and future versions of this and any other Advantage 2-related things I post will be at https://github.com/nicholasknight/adv2keyboard)
I received my Advantage 2 today. There's no full manual yet, even though keyboards are apparently arriving (hint, hint, Kinesis). The quick start guide leaves out the "power user mode", and there are some other quirks.
Update: A manual has been posted at http://www.kinesis-ergo.com/advantage2-resources/
It includes a dictionary for the key maps, but I know it leaves at least one possible key undocumented: it does not list f14, but I have successfully mapped my scrollock to f14 regardless.
It also mentions a firmware version (1.0.18) that doesn't seem to be available yet, with a new feature (status report playback speed).
http://aperiodic.net/screen/quick_reference
How to Navigate, copy & paste content?
within screen sessions: Cntl a + [ : To start navigation using up/down arrow Press Space bar: To select content starting position