Suppose you have weird taste and you absolutely want:
- your visual selection to always have a green background and black foreground,
- your active statusline to always have a white background and red foreground,
- your very own deep blue background.
Suppose you have weird taste and you absolutely want:
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
| Source material: | |
| http://security.stackexchange.com/questions/24444/what-is-the-most-hardened-set-of-options-for-gcc-compiling-c-c | |
| https://wiki.gentoo.org/wiki/Hardened_Gentoo | |
| https://wiki.debian.org/Hardening | |
| ================================================================================================================> | |
| GCC Security related flags and options: | |
| CFLAGS="-fPIE -fstack-protector-all -D_FORTIFY_SOURCE=2" | |
| LDFLAGS="-Wl,-z,now -Wl,-z,relro" |
Just migrated it from Codepen.io to markdown. Credit goes to David Conner.
| Working with DOM | Working with JS | Working With Functions |
|---|---|---|
| Accessing Dom Elements | Add/Remove Array Item | Add Default Arguments to Function |
| Grab Children/Parent Node(s) | Add/Remove Object Properties | Throttle/Debounce Functions |
| Create DOM Elements | Conditionals |
Picking the right architecture = Picking the right battles + Managing trade-offs
"How do I get started with Node?" is a commonly heard question in #Node.js. This gist is an attempt to compile some of the answers to that question. It's a perpetual work-in-progress.
And if this list didn't quite answer your questions, I'm available for tutoring and code review! A donation is also welcome :)
Before you get started learning about JavaScript and Node.js, there's one very important article you need to read: Teach Yourself Programming in Ten Years.
Understand that it's going to take time to learn Node.js, just like it would take time to learn any other specialized topic - and that you're not going to learn effectively just by reading things, or following tutorials or courses. _Get out there and build things!
| # to simplify life, install xclip and append the following lines to your .bashrc | |
| alias "c=xclip" # copy to X clipboard (register *) | |
| alias "cs=xclip -selection clipboard" # copy to system wide clipboard (register +) | |
| alias "v=xclip -o" # output copied content (paste) | |
| alias "vs=xclip -o -selection clipboard" # paste from system wide clipboard (equivalent to `v -selection clipboard`) | |
| # examples: | |
| # copy to X: | |
| # go to the same directory in terminal 2 as in terminal 1 | |
| # Terminal 1: |
From N1256: (See http://port70.net/~nsz/c/c99/n1256.html#J.2)
main using one of the specified forms (5.1.2.2.1).