common/locale/en-US/faq.xml

   1 <?xml version="1.0" encoding="UTF-8"?>
   2 <?xml-stylesheet type="text/xsl" href="dactyl://content/help.xsl"?>
   3
   4 <!DOCTYPE document SYSTEM "dactyl://content/dtd">
   5
   6 <document
   7     name="faq"
   8     title="&dactyl.appName; FAQ"
   9     xmlns="&xmlns.dactyl;"
  10     xmlns:html="&xmlns.html;">
  11
  12             <h1 style="margin-top: 0;">Frequently Asked Questions</h1>
  13             <p>
  14                 Below is a list of some of the commonest questions that come to
  15                 our attention, along with their hopefully satisfactory answers.
  16                 Please take a minute to search for your answers here before
  17                 asking the <link topic="&dactyl.list.href;">mailing list</link> or
  18                 <link topic="&dactyl.irc;">irc channel</link>,
  19                 and don't forget to peruse the
  20                 <link topic="&dactyl.hg.latest;&dactyl.name;/NEWS">NEWS file</link> for recent
  21                 changes that might throw you off balance.
  22             </p>
  23
  24             <toc start="2"/>
  25
  26             <h2 tag="faq-general">General</h2>
  27             <h3 tag="faq-fork">Why did Pentadactyl split from Vimperator?</h3>
  28             <p>
  29                 The reasons for the fork were mostly political, but mostly
  30                 boil down to the fact that the current maintainer, while
  31                 making no substantial contributions to the project for several
  32                 years, continues to exercise full editorial control while
  33                 actively soliciting donations with no transparency whatever.
  34                 We considered the latter especially a slight on both our
  35                 developers and our users, and after a considerable escalation
  36                 of the degree of offense felt compelled to leave the project.
  37             </p>
  38             <p>
  39                 However, though we could no longer justify supporting the
  40                 Vimperator project, we've invested considerable time and
  41                 energy into the code over these past several years and still
  42                 use and care about it. For that reason, we've decided to
  43                 publicly release our personal changes and continue to develop
  44                 the extension under a different name.
  45             </p>
  46
  47             <h3 tag="faq-differences">What differentiates Pentadactyl from Vimperator?</h3>
  48             <p>
  49                 The main difference is that Vimperator's most active
  50                 developers have moved on to Pentadactyl. More qualitative
  51                 changes may be found in the
  52                 <link topic="&dactyl.hg.latest;&dactyl.name;/NEWS">change log</link>,
  53                 but essentially add up to what we consider more active and
  54                 thoughtful development. Among the most visible differences, as
  55                 of Pentadactyl 1.0, are more extensive Firefox 4 support,
  56                 significantly better startup time and completion performance,
  57                 considerably better :sanitize and private mode support, a
  58                 greatly improved incremental find implementation, major
  59                 improvements in Ex command parsing (including the ability to
  60                 separate commands with | and split long commands across lines),
  61                 conditionals (<ex>:if</ex>/<ex>:else</ex>) in configuration
  62                 files, greatly updated documentation, and a number of bug fixes.
  63             </p>
  64
  65             <h3 tag="faq-statussymbols">What do the "[-+♥]" symbols in the status bar mean?</h3>
  66             <p>
  67                 These indicate that you can move backward through history,
  68                 that you can move forward through history, and that the page is
  69                 bookmarked, respectively. See also <ex>:help</ex>
  70                 <t>status-line</t>.
  71             </p>
  72
  73             <h3 tag="faq-lasttab">How can I prevent <k>d</k> on the last tab from closing the window?</h3>
  74             <p><ex>:set!</ex> <hl key="HelpOpt">browser.tabs.closeWindowWithLastTab</hl>=<hl key="Boolean">false</hl></p>
  75
  76             <h3 tag="faq-autocomplete"><strut/>How can I prevent the command line completion list showing until I press <k name="Tab" link="c_&lt;Tab>"/>?</h3>
  77             <p>
  78                 You can disable it entirely with <se opt="autocomplete"/> or for
  79                 specific types of command completion by choosing more
  80                 restrictive values. See <ex>:help</ex> <o>autocomplete</o> and
  81                 <o>wildmode</o>.
  82             </p>
  83
  84             <h3 tag="faq-editor-fork">Why doesn't external input field editing work with my <o>editor</o> setting?</h3>
  85             <p>
  86                 Unfortunately, external editors which return immediately, before
  87                 editing is complete, are not supported. This means that
  88                 <tt>gvim</tt>, for instance, must be run with the <em>-f</em>
  89                 flag, and editors run from a terminal must not connect to a
  90                 remote process. In the case of Rxvt-unicode, this means that the
  91                 <tt>urxvtc</tt> program is not an option, and Gnome Terminal is
  92                 very likely not useable under any circumstances.
  93             </p>
  94             <note>
  95                 If you are using a version of Firefox newer than 4.0 beta 7 and
  96                 a version of Pentadactyl less than 1.0 βeta 4, you'll need to
  97                 upgrade the latter.
  98             </note>
  99
 100             <h3 tag="faq-symlinks">Why can't I build/install from the Mercurial repository on Windows®?</h3>
 101             <p>
 102                 We use symbolic links in our repository to deal with certain
 103                 files which are common across projects. Mercurial for Windows®,
 104                 unfortunately, doesn't deal with these very well. However,
 105                 adding the following lines to the <tt>.hg\hgrc</tt> file in your
 106                 repository should make things work:
 107             </p>
 108             <code><hl key="Key">[hooks]</hl>
 109 update = <str delim="">python:common/contrib/fix_symlinks.py:fix_symlinks</str>
 110 preupdate = <str delim="">python:common/contrib/fix_symlinks.py:fix_symlinks</str>
 111 commit = <str delim="">python:common/contrib/fix_symlinks.py:fix_symlinks</str>
 112 precommit = <str delim="">python:common/contrib/fix_symlinks.py:fix_symlinks</str></code>
 113
 114             <h2 tag="faq-open"><ex>:open</ex> behavior</h2>
 115             <h3 tag="faq-urlsep">Why can't I separate URLs in <ex>:open</ex> with a comma anymore?</h3>
 116             <p>See <ex>:help <o>urlseparator</o></ex></p>
 117
 118             <h3 tag="faq-hidden-engines">
 119                 <strut/>
 120                 <ex>:open <a>search-string</a></ex> or <ex>:open <str delim="">google</str> <a>search-string</a></ex>
 121                 results in <str>The url is not valid and cannot be loaded</str>
 122             </h3>
 123             <p>
 124                 You need a valid search engine name in the <o>defsearch</o>
 125                 option. If it's stopped working suddenly, there's a good chance
 126                 that you've either deleted a search engine or changed its alias.
 127                 You can check by invoking
 128
 129                 <code><ex>:dialog <str delim="">searchengines</str></ex></code>
 130
 131                 There also appears to be a Firefox bug whereby the default
 132                 engines are hidden after an update. This can be remedied by
 133                 invoking
 134
 135                 <code style="position: relative"><ex>:js</ex> services.browserSearch.getEngines().forEach(<em>function</em> (e) e.hidden = <hl key="Boolean">false</hl>)</code>
 136             </p>
 137
 138             <h2 tag="faq-keys">Key bindings</h2>
 139             <h3 tag="faq-website-keys">How can I use the native key bindings of sites like Gmail?</h3>
 140             <p>
 141                 See the <o>passkeys</o> option to automatically pass specific
 142                 keys on sites of your choosing, or <t>autocmd-examples</t> to
 143                 automatically enter <em>Pass Through</em> mode for certain websites.
 144             </p>
 145
 146             <h3 tag="faq-passkeys-autocmd">Why doesn't my modes.passAllKeys autocmd work anymore?</h3>
 147             <p>See <t>faq-website-keys</t> above.</p>
 148
 149             <h2 tag="faq-hints">Hints</h2>
 150             <h3 tag="faq-hintkeys">How can I use keys other than numbers for hinting?</h3>
 151             <p>Use the <o>hintkeys</o> option.</p>
 152
 153             <h3 tag="faq-hintkeys-uppercase"><strut/>How can I display my hints in upper case but type them in lower case?</h3>
 154             <p>
 155                 If you use alphabetic characters for your <o>hintkeys</o> and
 156                 would like to be able to type them in lower case but still have
 157                 the hints displayed in upper case, use:
 158             </p>
 159             <code><ex>:highlight</ex> <em>-a</em> Hint <hl key="Key">text-transform</hl>: <str delim="">uppercase</str>;</code>
 160
 161             <h3 tag="faq-hint-hidetext">How can I hide the hint text for input and image hints?</h3>
 162             <p>
 163                 If you'd only like to show the numbered portion of hints, you
 164                 can do so with:
 165             </p>
 166             <code><ex>:highlight</ex> Hint<str delim="">::after</str> <hl key="Key">content</hl>: attr(<str delim="">number</str>) <hl key="Key">!important</hl>;</code>
 167
 168 </document>
 169
 170 <!-- vim:se sts=4 sw=4 et: -->