"this.contexts = { "/": this }" in CompletionContext(...)
was causing ":set defsearch=google<cr>" (and similar) to error
with infinite recursion. Restoring to
"this.contexts = { name: this }" fixes the problem, but does it
break other things?
Please review.
a.) Cleaned up copyright language to match conventions.
(I used the memoir document class documentation as a reference, but
these conventions are common throughout publishing)
* The (c) symbol has no legal meaning. Only the word "Copyright" and
an encircled lowercase c are appropriate. So the word "Copyright"
was placed before each (c).
* Each (C) was changed to (c).
* Kris uses the correct symbols in copyright notices, but those
symbols can be problematic in terminal-mode editors. Added the word
"Copyright" as well.
* Replaced colons/spaces after years with the word "by."
b.) Added a copyright notice to common/content/template.js. It was
missing one entirely. Please correct if it doesn't need one or if the
copyright isn't held by Martin.
c.) Also added a "tildetidy" target to Makefile common that includes a
version of the find line from the existing "clean" target (however,
this version uses "rm -fv" instead of "rm -f").
is that once you know which :dialog you want to open, you can usually
open it with :dia xy<tab> very quickly and reliable. The difference
to :emenu is that :emenu has lots of completion items with the same
prefix, so anchored completions wouldn't really be that helpful to
quickly open a menu.
This reverts commit fa842fd716aac599891a53efdf64cab76422c153.
Until liberator.NEW_BACKGROUND_TAB operates differently based on the
setting of browser.tabs.loadInBackground, this code must remain. At
the moment, NEW_BACKGROUND_TAB only opens a true background tab if
loadInBackground=true. When loadInBackground=false, the meaning of
NEW_TAB and NEW_BACKGROUND_TAB flip. Hence, until they're invariant,
something like ;F (which must always load tabs in the background)
has to pay attention to loadInBackground.
incremental results, and the user gets more completion, the more often
he presses tab. Need to find out, how to change the "Waiting..." message
to "More results...". Also reminds me, how ugly the completion context
code is partly. We should try to clean it up and remove/merge useless
function to make it's interface smaller and more side-effect free.
