Mostly typos/omissions/markup errors, more remarkable e. g. changing
'b' to 'B' in tutorial reflecting a change from 1.2.
Also uncommented [macros] section in asciidoc.conf (is that right?).
Signed-off-by: Doug Kearns <dougkearns@gmail.com>
* Delete the desctiption of nonexistent command :highlight-clear.
* Delete the erroneous info about bang of :highlight command.
* Add unwritten group names from styling.js.
Signed-off-by: Kris Maglione <maglione.k@gmail.com>
This commit is in the spirit of
a3fc60c011b8ed42c2efec2147b1268abc10d578.
Vim's help format really numbers everything manually? Sections too?
That's unbelievable.
Also added rough documentation for insert mode.
TODO: Abbreviations should also expand on <CR> and <Tab>, but right now
adding <CR> to the mappings.add() has no effect, and adding <Tab> to the
mappings.add() breaks tab completion.
TODO: Rather than listing non-keyword characters in two places (ui.js
and mappings.js), they should be specified in one location (that could
someday be trumped by an 'iskeyword' option).
This reverts commit a401e3ebf34c964ca508c189e1daf9b0b18e57b9.
Explicit numbering is easier to read, and will likely be required if and when
we switch to Vim's help format.
At the moment, only "syntax=asciidoc" was specified. The
asciidoc_filetype.vim that is distributed with Asciidoc gives the
installer two options -- to either associate every *.txt file with
asciidoc or to try to decipher whether or not the file is an asciidoc
using the first 50 lines.
So it's not given that a developer will open the *.txt files with
ft=asciidoc, and so it's helpful to have it explicitly in the modeline.
Again, by Chicago Manual of Style (CMOS) and several other style guides, we
hyphenate compound /modifiers/ when they come /before/ the word being
modified.
So the "command line" is not hyphenated, but the "command-line mode" is.
This is consistent with Vim help style conventions as well.
This reverts commit 1455b9d27224b1289e7762fef3c4d158c7074877.
"Command line" should only be hyphenated when it is a /leading/ compound
/modifier/. For example, "command-line interface." See CMOS (or
Strunk/White) for more information.
Automatic numbering exists for a reason. It's more elegant and easy to
manage. Additionally, because numbering rules can be specified centrally,
it adds consistency to the final look of the documents. An editor shouldn't
have to think about the current numbering level or number. That should be
handled by asciidoc as it builds the final doc.
[ However, added explicit first number to make list source code look a
little better. ]
Also moved $VIMPERATOR_INIT keyword to its correct location in
starting.txt.
This change partially reverts changeset a1f264639f27d7d5b87e5fbccf54d6890a03ca7d.
For now, the internal equivalent of "iskeyword" is [^\s'"].
In the future, the internal "iskeyword" equivalent can be expanded. It may
be overboard to add an "iskeyword" option, as it applies to lots more
things than :abbr. Additionally, it's not clear why it's bad to call
keyword characters everything except whitespace and quotes.
TODO: Should abbreviations be triggered by any non-keyword character?
TODO: Should abbreviations be triggered by <CR>?
TODO: Should abbreviations be able to include <Left>, etc.?
