See http://vimperator.org/trac/ticket/126
Using...
function (args)
{
let args = args.string;
...
was causing Firefox to complain that args was undefined. Changing the
"let" to "var" or changing the names of the variables (e.g., changing
"function (args)" to "function (arg)") fixes the problem. IMO, this
appears to be a bug in Firefox.
The short fix would be to change the formal argument from "args" to
"arg." However, that would make delmarks' implementation different from
all the rest. So changed "let args" to "let argstring" and adjusted
throughout the function.
* The stdin - wasn't needed. However, an ||true is now used to prevent
Makefile from erroring out (I'm sure there's a better way).
* muttatorrc was spelled muttatororrc; fixed now.
* The vimperator.vba was not included although muttator.vba was.
* Adjusted Makefiles so that vim is called with "-" to open stdin (that
was required on my Vim7.2 system; does it break others?)
This also adds a quick 'n' dirty build mechanism for creating the
Vimballs. Unfortunately, these aren't particularly amenable to being
created in a batch process. Dr Chip has created a small C program for
this but that would be a silly dependency.
Files like vimperator.vim, javascript.vim, and vimperatorrc.example
might fit better in a "contrib" directory. It's not clear whether there
should be vimperator/contrib and muttator/contrib directories or a
single liberator/contrib directory.
The Makefile.common doesn't include these files in the bundle, and so it
doesn't seem like a bad idea to package them in a single
liberator/contrib directory with a CONTENTS or README file giving a ToC
for the directory.
* Require language part of locale to be two lowercase letters.
* Update Makefile.doc comment -- add "include" comment.
* Get rid of muttator/locale/en-US/Makefile symlink in favor of include.
* 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.
