- Combined the last 2 commands into a single format that can be expanded upon
by showing the -o option, since both can be passed as options.
- This also does not increase the no. of examples.
- Corrected a minor typo in path.
Instead, explain additional keystrokes in the example title. See
ee1472e76f (r82836295)
Also, change order of examples to down/up, end/start and next/previous
to keep consistency.
* vim: Improvements we can can agree on
Remove spaces between keypresses (as it could lead users to think they
should type a space there).
Simplify regexp substitution example.
Add ...then... to search example.
Add quit without saving example.
* vim: Improvements we can can agree on
Move search keystrokes to the example title.
Keep original regexp substitution example. See conversation starting at
ee1472e76f (r82820204)
I tried to condense the most useful basic commands into this page without surpassing our length limit.
I also expanded the main description -- I wonder if there's a way to phrase it which could allow us to get rid of all the <Esc>s...
I combined copy/cut/paste into a single command, since it was important to allow space for a slightly more advanced command, (the find/replace example), which introduces some important vim concepts, such as command application ranges.
- reorganize examples for a more logical progression
- make descriptions clearer and more in line with the option names they describe (c.f. #782 and #1018)
- Download: first example introduces `-o`, second one introduces `-O`,
third example introduces `-L` and `-C` using brackets as per #1018
- Data: first example introduces `-d` (default method is POST and
default Content-Type is application/x-www-form-urlencoded), second
example introduces `-X` and `-H`
- Remove "Head request"
- Expand description of "Send form-encoded data" example
- Use same description for the "Download a URL to a file" example as for curl (see #1019 and #1023)
- Also fix example formatting
* wget: Use "contents" instead of "output" of an URL
- Difference between a stash name and a stash message was not clear. For
example, you cannot do:
$ git stash save foo
$ git stash apply foo
fatal: ambiguous argument 'foo': unknown revision or path not in
the working tree.
- Difference between stash `apply` and `pop` was not clear
- Make it clearer that all `apply`, `pop` and `drop` can take an
optional stash name, and that the default name is `stash@{0}`
* add page with examples for apg (advanced password generator)
* edits per code review
* spread the examples across more options than just -m and -M
* expand abbreviations and add double curly brackets
- changed token syntax to match project guidelines
- added tokens to the rename example
- moved rename example to before the delete example
- reword some descriptions for clarity
- include "git" in the command description
* Updates vim and vimtutor pages
* Easy peasy.
* Use <Enter> instead of <Cr>
* Show help command.
We might not be able to help you move around
but the interactive help provided by vim is
pretty good, so helping people find it might
be a good idea.
* Reorder commands and lowercase help
Doing a reverse DNS lookup by typing out the IP address in reverse, plus adding .in-addr.arpa to the end is tedious, but fortunately dig has the -x option which makes that process much simpler as one can just feed it a normal IP address.
* psql: Improve page
- Removed * , this was causing problems with rendering. The node client was
gobbling up the entire word !
- Changed 'query' to 'command' as it can be a postgres db command too.
- Used the -f flag for running multiple commands as its a better and scalable
option.
* Addressing comments
* Replacing against with on
- Mentioning the default user
* rm: various tweaks for clarity; add -v
changed some descriptions and tokens to make the meaning of each command clearer, and facilitate memorization of the flags
added the -v (verbose) option
* use a more intuitive pattern for the -i option
* Applying the snake_case convention throughout the repo
- Also removing the file extension where not needed
- Adding {{ }} on a few old pages
* Addressing concerns
- Added {{ }} where they were missed out
- Removed spaces inside {{ }}
- Reverting "file" to "filename" to make it clearer
* Fixing the comments on nc page
Numbered field references have been used in the first two examples,
so it's quite reasonable to take the opportunity to introduce a new (and quite useful!) concept.
In addition, this commit makes a few tweaks to the example descriptions, to make them clearer.
This involves another command, but it's such a natural extension of uniq's `-c` functionality that I feel it's warranted to show here.
We should probably add a sort to the -c example too, because uniq only deals with *sequential* line repetitions.
By default, grep already uses regular expressions when searching.
The example `grep -e {{^regex$}} {{path/to/file}}` is the same as `grep {{^regex$}} {{path/to/file}}`.
However, because of the comment about extended regular expressions, I mistakenly assumed `-e` was the option to enable it.
I believe most people would refer to `tldr` in this use case looking for the `-E` extended regular expressions.
With this in mind, I believe that example would be better rephrased as this pull request makes it.
This chage adds examples for exporting public and private GPG keys.
This is particularly useful for backing up keys. In both cases they have
been output as ASCII armored text with the `--armor` flag to make the
output easier to work with.
