+ Below is a list of some of the commonest questions that come to + our attention, along with their hopefully satisfactory answers. + Please take a minute to search for your answers here before + asking the mailing list or + irc channel, + and don't forget to peruse the + NEWS file for recent + changes that might throw you off balance. +
+ ++ The reasons for the fork were mostly political, but mostly + boil down to the fact that the current maintainer, while + making no substantial contributions to the project for several + years, continues to exercise full editorial control while + actively soliciting donations with no transparency whatever. + We considered the latter especially a slight on both our + developers and our users, and after a considerable escalation + of the degree of offense felt compelled to leave the project. +
++ However, though we could no longer justify supporting the + Vimperator project, we've invested considerable time and + energy into the code over these past several years and still + use and care about it. For that reason, we've decided to + publicly release our personal changes and continue to develop + the extension under a different name. +
+ +
+ The main difference is that Vimperator's most active
+ developers have moved on to Pentadactyl. More qualitative
+ changes may be found in the
+ change log,
+ but essentially add up to what we consider more active and
+ thoughtful development. Among the most visible differences, as
+ of Pentadactyl 1.0, are more extensive Firefox 4 support,
+ significantly better startup time and completion performance,
+ considerably better :sanitize and private mode support, a
+ greatly improved incremental find implementation, major
+ improvements in Ex command parsing (including the ability to
+ separate commands with | and split long commands across lines),
+ conditionals (
+ These indicate that you can move backward through history,
+ that you can move forward through history, and that the page
+ is bookmarked, respectively. See also
+ Regular expression search is possible with the /Find Bar/
+ extension installed, in which case it can be toggled with the
+ \r and \R search flags. See also
+
+ You can disable it entirely with
+ Unfortunately, external editors which return immediately, + before editing is complete, are not supported. This means that + gvim, for instance, must be run with the -f flag, and + editors run from a terminal must not connect to a remote + process. In the case of Rxvt-unicode, this means that the + urxvtc program is not an option, and Gnome Terminal is very + likely not useable under any circumstances. +
++ We use symbolic links in our repository to deal with certain + files which are common across projects. Mercurial for + Windows®, unfortunately, doesn't deal with these very well. + However, adding the following lines to the .hg\hgrc + file in your repository should make things work: +
+[hooks]
+update = python:common/contrib/fix_symlinks.py:fix_symlinks
+preupdate = python:common/contrib/fix_symlinks.py:fix_symlinks
+commit = python:common/contrib/fix_symlinks.py:fix_symlinks
+precommit = python:common/contrib/fix_symlinks.py:fix_symlinks See
+ You need a valid search engine name in the
+ See the
See
Use the
+ If you use alphabetic characters for your
:highlight -a Hint text-transform : uppercase ;+ If you'd only like to show the numbered portion of hints, you + can do so with: +
+:highlight Hint::after content : attr(number ) !important ;