| #! /bin/sh | |
| ### BEGIN INIT INFO | |
| # Provides: redis-server | |
| # Required-Start: $syslog | |
| # Required-Stop: $syslog | |
| # Should-Start: $local_fs | |
| # Should-Stop: $local_fs | |
| # Default-Start: 2 3 4 5 | |
| # Default-Stop: 0 1 6 | |
| # Short-Description: redis-server - Persistent key-value db |
| plugin | |
| naming convention: name_of_plugin.vim | |
| these files are sourced for all file types | |
| doc | |
| naming convention: name_of_plugin.txt | |
| these files document the functionality of a plugin | |
| color | |
| naming convention: name_of_colorscheme.vim |
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.
| [ | |
| { | |
| "code": "AAA", | |
| "lat": "-17.3595", | |
| "lon": "-145.494", | |
| "name": "Anaa Airport", | |
| "city": "Anaa", | |
| "state": "Tuamotu-Gambier", | |
| "country": "French Polynesia", | |
| "woeid": "12512819", |
I use tmux splits (panes). Inside one of these panes there's a Vim process, and it has its own splits (windows).
In Vim I have key bindings C-h/j/k/l set to switch windows in the given direction. (Vim default mappings for windows switching are the same, but prefixed with C-W.) I'd like to use the same keystrokes for switching tmux panes.
An extra goal that I've solved with a dirty hack is to toggle between last active panes with C-\.
Here's how it should work:
| #!/bin/sh | |
| git_repo=$1 | |
| [ -z "$git_repo" ] && git_repo="." | |
| cd $git_repo > /dev/null 2>&1 | |
| if [ $? -ne 0 ]; then | |
| printf "Invalid directory path.\n" | |
| exit 1 | |
| fi |
| /** | |
| * @apiDefineStructure ${NAME}Params | |
| * @apiParam {String} slug ${MODEL} identifier | |
| */ | |
| /** | |
| * @apiDefineStructure ${NAME}Success | |
| * @apiSuccess {String} slug ${MODEL} identifier | |
| * @apiSuccess {Date} createdAt Date of document creation. | |
| * @apiSuccess {Date} updatedAt Date of document last change. | |
| */ |
This is a guide on how to email securely.
There are many guides on how to install and use PGP to encrypt email. This is not one of them. This is a guide on secure communication using email with PGP encryption. If you are not familiar with PGP, please read another guide first. If you are comfortable using PGP to encrypt and decrypt emails, this guide will raise your security to the next level.
This is a collection of snippets, not a comprehensive guide. I suggest you start with Operational PGP.
Here is an incomplete list of things that are different from other approaches:
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent