- expand description of local and global options
- adjust example descriptions for clarity
- change the descriptions of the get/set/remove examples to be more generic
- change the alias example to a more useful one
- use "configuration entries" instead of "configuration options" to match both preset options and aliases
* valgrind: add page
* valgrind: tweak Memcheck example
Provide alternate, clearer syntax that functions the same and update
description accordingly.
* valgrind: correct program description
* valgrind: add list of common tools
* valgrind: remove general form example and add no-option example
* valgrind: replace period with colon in example 1
* Include gist page
* Fix linting errors
* Quote "hello world" in the echo commnad
* Change wording to make explanation clearer
* Further simplify descriptions of gist command
* Simplify description of the update gist command
- hugo -> Hugo
- lowercase the description
- plain URL
- remove the extension token
- do not use relative references
- modify the buildDraft example to standalone and change the wording slightly
- modify the "watch for changes" wording slightly
- Add in `hugo` commands essential to getting a site up and running.
- This is defined as:
- A site existing
- A theme existing
- A page existing
- The site being built in some manner (optionally being served through the webserver)
First pass on verbage.
For completeness: the -0 option is actually used to specify the input record separator (as an octal number).
Without it, the record separator is the newline character, i.e. the files are processed line by line
(which doesn't allow find-replace expressions that include newlines to work).
According to the [documentation](http://perldoc.perl.org/perlrun.html#Command-Switches),
using plain `-0` is not guaranteed to have the effect of parsing the entire file,
because if the file does contain characters with octal value equal to the parameter passed to (or implied by) the -0 option,
these characters will be treated as line breaks.
However, if the value exceeds 377<sub>8</sub> (i.e. 255), it won't be matched to characters on the file.
777 is the preferred convention within that exceptional range, as the highest value that keeps to 3 octal digits.
Here we're forgoing such details and using -0 anyway, since for most cases this will be enough.
* pygmentize: various tweaks
- adjust punctuation in main description and first example's description
- mention "list" (rather than "show") in the -L examples, to improve memorability
- explain what lexers are
- clarify which of the parameters are input and output filenames
- simplify last example
* make -O example more didactic
References:
- http://pygments.org/docs/cmdline/#options-and-filters
- http://pygments.org/docs/formatters/#HtmlFormatter
* pygmentize: changes per code review
* pygentize: fix typos
As described in http://stackoverflow.com/a/9537923 (paraphrased below):
> You need to create a local branch that tracks a remote branch.
> The following command will create a local branch
> tracking the remote branch of the same name.
> When you push your changes the remote branch will be updated.
>
> `git checkout --track [remotename]/[branch]`
>
> This is a shorthand for `git checkout -b [branch] [remotename]/[branch]`.
>
> For git 1.7.2.3 and higher this is enough: `git checkout daves_branch`
>
> Note that with recent git versions,
> **this will command not create a local branch and will put you in a 'detached HEAD' state.**
> If you want a local branch, use the --track option.
> Full details here: http://git-scm.com/book/en/v2/Git-Branching-Remote-Branches#Tracking-Branches
