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.?
this really just is a small commit which looks done right and satisfies
the need of a lot of people.
This reverts commit 969feba9355bdc148dc9403992facb314a30d1be.
This should have been discussed first, especially given the current feature
freeze. This could easily have been implemented as a plugin. Feel free to
re-commit to the dev branch *after* discussing it, though.
This reverts commit da2ab0f1abe0f110d71fbed5c10c165565f76100.
The implementation provides the same functionality as ;F while still
maintaining the Vimp2.0 style hints. There is definitely room for
refactoring here.
Fix#110 (;b and ;t don't respond to 'activate'. Behavior spec'd in
:help is unclear).
I've fixed the inverted ;b/;t behaviour (the bug), closed the ticket,
and added 'activate' support as a TODO.
Most of the special case asciidoc replacements were also removed since
they're a bit confusing and doing so results in a 60% improvement in the
time taken by asciidoc to process the help pages. Unfortunately, I'm
now limited to preparing a three course menu for my guests while it runs
rather than the degustation extravaganzas of the past but such is life.
It's still a bit of a mess but since we're almost certainly moving to
something else in the near future it's probably not worth cleaning it up
before 2.0 is released.
