mirror of
https://github.com/gryf/pentadactyl-pm.git
synced 2026-02-11 17:25:46 +01:00
Rename appname/idname to appName/idName in help files to maintain parity with code.
This commit is contained in:
Kris Maglione
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="all"
|
||||
title="&dactyl.appname; All"
|
||||
title="&dactyl.appName; All"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<tags>all</tags>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="autocommands"
|
||||
title="&dactyl.appname; Autocommands"
|
||||
title="&dactyl.appName; Autocommands"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="autocommands">Automatic commands</h1>
|
||||
|
||||
@@ -5,17 +5,17 @@
|
||||
|
||||
<document
|
||||
name="browsing"
|
||||
title="&dactyl.appname; Browsing"
|
||||
title="&dactyl.appName; Browsing"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="surfing browsing">Browsing</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<h2 tag="bypassing-&dactyl.name;">Bypassing &dactyl.appname;</h2>
|
||||
<h2 tag="bypassing-&dactyl.name;">Bypassing &dactyl.appName;</h2>
|
||||
|
||||
&dactyl.appname; overrides nearly all &dactyl.host; keys in order to
|
||||
&dactyl.appName; overrides nearly all &dactyl.host; keys in order to
|
||||
make browsing more pleasant for Vim users. On the occasions when you
|
||||
want to bypass &dactyl.appname;'s key handling and pass keys directly to
|
||||
want to bypass &dactyl.appName;'s key handling and pass keys directly to
|
||||
&dactyl.host; or to a web page, you have two options:
|
||||
|
||||
<item>
|
||||
@@ -465,7 +465,7 @@ want to bypass &dactyl.appname;'s key handling and pass keys directly to
|
||||
<spec>:quita<oa>ll</oa></spec>
|
||||
<description>
|
||||
<p>
|
||||
Quit &dactyl.appname;, no matter how many tabs/windows
|
||||
Quit &dactyl.appName;, no matter how many tabs/windows
|
||||
are open. The session is not stored.
|
||||
</p>
|
||||
</description>
|
||||
@@ -519,7 +519,7 @@ want to bypass &dactyl.appname;'s key handling and pass keys directly to
|
||||
<spec>ZZ</spec>
|
||||
<description short="true">
|
||||
<p>
|
||||
Quit &dactyl.appname; and save the session. Works like
|
||||
Quit &dactyl.appName; and save the session. Works like
|
||||
<ex>:xall</ex>.
|
||||
</p>
|
||||
</description>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="buffer"
|
||||
title="&dactyl.appname; Buffer"
|
||||
title="&dactyl.appName; Buffer"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="buffer document">Buffer</h1>
|
||||
|
||||
@@ -5,18 +5,18 @@
|
||||
|
||||
<document
|
||||
name="cmdline"
|
||||
title="&dactyl.appname; Command-line"
|
||||
title="&dactyl.appName; Command-line"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="command-line-mode command-line mode-cmdline">Command-line mode</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname;'s command-line mode is perhaps its most
|
||||
&dactyl.appName;'s command-line mode is perhaps its most
|
||||
powerful interface. In this mode, the command input bar at the
|
||||
bottom of the window is given the keyboard focus for any of a
|
||||
variety of required inputs. In addition to access to almost
|
||||
every aspect of &dactyl.appname; and &dactyl.host;, the command
|
||||
every aspect of &dactyl.appName; and &dactyl.host;, the command
|
||||
line provides power and comprehensive completion for all of its
|
||||
commands, along with concise descriptions for each command and
|
||||
all of its arguments. Couple this with persistent, searchable
|
||||
|
||||
@@ -7,7 +7,7 @@
|
||||
|
||||
<document
|
||||
name="developer"
|
||||
title="&dactyl.appname; Developer information"
|
||||
title="&dactyl.appName; Developer information"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="developer-information">Developer information</h1>
|
||||
@@ -67,7 +67,7 @@
|
||||
<dt>&tab;@topic</dt> <dd>The topic of the link. Either a help topic or a fully-qualified URI.</dd>
|
||||
<dt>em</dt> <dd><em>Emphasized</em> text. (HelpEm)</dd>
|
||||
<dt>str</dt> <dd>A <str>string</str>, with its contents wrapped in quotes. (HelpString)</dd>
|
||||
<dt>logo</dt> <dd>&dactyl.appname;'s logo. (Logo)</dd>
|
||||
<dt>logo</dt> <dd>&dactyl.appName;'s logo. (Logo)</dd>
|
||||
</dl>
|
||||
<dl>
|
||||
<dt>Items</dt><dd/>
|
||||
@@ -109,7 +109,7 @@
|
||||
<dt>&tab;@summary</dt> <dd>A short description of the plugin, shown in its section head.</dd>
|
||||
|
||||
<dt>project</dt> <dd>The project for which this plugin was intended.</dd>
|
||||
<dt>&tab;@name</dt> <dd>The name of the project (i.e., <str>&dactyl.appname;</str>)</dd>
|
||||
<dt>&tab;@name</dt> <dd>The name of the project (i.e., <str>&dactyl.appName;</str>)</dd>
|
||||
<dt>&tab;@minVersion</dt> <dd>The minimum version of the project for which this plugin is intended to work.</dd>
|
||||
<dt>&tab;@maxVersion</dt> <dd>The maximum version of the project for which this plugin is intended to work.</dd>
|
||||
|
||||
@@ -133,9 +133,9 @@
|
||||
<h2 tag="writing-plugins">Writing plugins</h2>
|
||||
|
||||
<p>
|
||||
Writing &dactyl.appname; plugins is incredibly simple. Plugins are
|
||||
Writing &dactyl.appName; plugins is incredibly simple. Plugins are
|
||||
simply JavaScript files which run with full chrome privileges and
|
||||
have full access to the &dactyl.appname; and &dactyl.host; APIs.
|
||||
have full access to the &dactyl.appName; and &dactyl.host; APIs.
|
||||
Each plugin has its own global object, which means that the
|
||||
variables and functions that you create won't pollute the global
|
||||
<em>window</em> or private <em>dactyl</em> namespaces. This means
|
||||
@@ -153,11 +153,11 @@
|
||||
that, what you may do with your plugins is practically limitless.
|
||||
Plugins have full access to all of the chrome resources that
|
||||
ordinary &dactyl.host; does, along with the entire power of the
|
||||
&dactyl.appname; API. If you need a starting point, have a look at some
|
||||
&dactyl.appName; API. If you need a starting point, have a look at some
|
||||
<link topic="&dactyl.plugins;">existing plugins</link> or
|
||||
<link topic="http://addon.mozilla.org/">extensions</link>,
|
||||
especially the
|
||||
<link topic="&dactyl.code;source/browse/">&dactyl.appname;</link>
|
||||
<link topic="&dactyl.code;source/browse/">&dactyl.appName;</link>
|
||||
source.
|
||||
</p>
|
||||
|
||||
@@ -209,7 +209,7 @@ XML.prettyPrinting = <hl key="Boolean">false</hl>;
|
||||
The inline XML is made possible by
|
||||
<link topic="https://developer.mozilla.org/en/E4X">E4X</link>.
|
||||
It is important that the documentation be assigned to the
|
||||
<em>INFO</em> variable, or &dactyl.appname; will not be able
|
||||
<em>INFO</em> variable, or &dactyl.appName; will not be able
|
||||
to find it. The XML property changes are not compulsory, but
|
||||
they do prevent certain formatting problems that may occur
|
||||
otherwise. Beginning your file with <str>use strict</str>, while
|
||||
@@ -218,7 +218,7 @@ XML.prettyPrinting = <hl key="Boolean">false</hl>;
|
||||
|
||||
<p>
|
||||
The documentation that you provide behaves exactly as other
|
||||
&dactyl.appname; documentation, which means that the tags you
|
||||
&dactyl.appName; documentation, which means that the tags you
|
||||
provide are available via <ex>:help</ex> with full tag
|
||||
completion and cross-referencing support. Although documentation
|
||||
is not required, we strongly recommend that all plugin authors
|
||||
|
||||
@@ -5,20 +5,20 @@
|
||||
|
||||
<document
|
||||
name="eval"
|
||||
title="&dactyl.appname; Expression Evaluation"
|
||||
title="&dactyl.appName; Expression Evaluation"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="expression expr eval javascript">Expression evaluation</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
Much of the power of &dactyl.appname; lies in its scriptable expression
|
||||
evaluation. &dactyl.appname; understands two kinds of expressions: ex
|
||||
Much of the power of &dactyl.appName; lies in its scriptable expression
|
||||
evaluation. &dactyl.appName; understands two kinds of expressions: ex
|
||||
commands, and JavaScript. Ex commands are simple, easy to type, and
|
||||
readily accessible from the <t>command-line</t>. They form a core part of
|
||||
the user interface. JavaScript, on the other hand, is much less
|
||||
straightforward, but allows for any number of complex actions to be
|
||||
executed, with full access to all of the internals of &dactyl.appname; and
|
||||
executed, with full access to all of the internals of &dactyl.appName; and
|
||||
&dactyl.host;. Both expression evaluation methods support sophisticated
|
||||
expression completion, including option lists and descriptions thereof,
|
||||
along with paren matching and syntax error highlighting.
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="gui"
|
||||
title="&dactyl.appname; GUI"
|
||||
title="&dactyl.appName; GUI"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:dactyl="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
@@ -13,7 +13,7 @@
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
Although &dactyl.appname; offers access to the most frequently used
|
||||
Although &dactyl.appName; offers access to the most frequently used
|
||||
&dactyl.host; functionality via Ex and Normal mode commands, there may be
|
||||
times when direct access to the &dactyl.host; GUI is required. For such
|
||||
eventualities, there are commands to access menu items and to launch
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="hints"
|
||||
title="&dactyl.appname; Hints"
|
||||
title="&dactyl.appName; Hints"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="quick-hints hints">Hints</h1>
|
||||
@@ -13,7 +13,7 @@
|
||||
|
||||
<p>
|
||||
Hints are an easy way to interact with web pages without using
|
||||
your mouse. In hint mode, &dactyl.appname; highlights and
|
||||
your mouse. In hint mode, &dactyl.appName; highlights and
|
||||
numbers all clickable elements. The elements can be selected
|
||||
either by typing their numbers, or typing parts of their text to
|
||||
narrow them down. While the default action is to click the
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="index"
|
||||
title="&dactyl.appname; Index"
|
||||
title="&dactyl.appName; Index"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="index">Index</h1>
|
||||
@@ -37,7 +37,7 @@ This file contains a list of all available commands, mappings and options.
|
||||
<dt><k name="C-u"/></dt> <dd>Scroll window upwards in the buffer</dd>
|
||||
<dt><k name="C-v"/></dt> <dd>Pass through next key</dd>
|
||||
<dt><k name="C-x"/></dt> <dd>Decrement last number in URL</dd>
|
||||
<dt><k name="C-z"/></dt> <dd>Temporarily ignore all &dactyl.appname; key bindings</dd>
|
||||
<dt><k name="C-z"/></dt> <dd>Temporarily ignore all &dactyl.appName; key bindings</dd>
|
||||
</dl>
|
||||
|
||||
|
||||
@@ -275,7 +275,7 @@ This file contains a list of all available commands, mappings and options.
|
||||
<dt><ex>:hardcopy</ex></dt> <dd>Print current document</dd>
|
||||
<dt><ex>:help</ex></dt> <dd>Open the help page</dd>
|
||||
<dt><ex>:helpall</ex></dt> <dd>Open the single unchunked help page</dd>
|
||||
<dt><ex>:highlight</ex></dt> <dd>Style &dactyl.appname;</dd>
|
||||
<dt><ex>:highlight</ex></dt> <dd>Style &dactyl.appName;</dd>
|
||||
<dt><ex>:history</ex></dt> <dd>Show recently visited URLs</dd>
|
||||
<dt><ex>:iabbrev</ex></dt> <dd>Abbreviate a key sequence in Insert mode</dd>
|
||||
<dt><ex>:iabclear</ex></dt> <dd>Remove all abbreviations in Insert mode</dd>
|
||||
@@ -314,7 +314,7 @@ This file contains a list of all available commands, mappings and options.
|
||||
<dt><ex>:qmark</ex></dt> <dd>Mark a URL with a letter for quick access</dd>
|
||||
<dt><ex>:qmarks</ex></dt> <dd>Show all QuickMarks</dd>
|
||||
<dt><ex>:quit</ex></dt> <dd>Quit current tab</dd>
|
||||
<dt><ex>:quitall</ex></dt> <dd>Quit &dactyl.appname;</dd>
|
||||
<dt><ex>:quitall</ex></dt> <dd>Quit &dactyl.appName;</dd>
|
||||
<dt><ex>:redraw</ex></dt> <dd>Redraw the screen</dd>
|
||||
<dt><ex>:reload</ex></dt> <dd>Reload the current web page</dd>
|
||||
<dt><ex>:reloadall</ex></dt> <dd>Reload all tab pages</dd>
|
||||
@@ -332,7 +332,7 @@ This file contains a list of all available commands, mappings and options.
|
||||
<dt><ex>:source</ex></dt> <dd>Read Ex commands from a file</dd>
|
||||
<dt><ex>:stop</ex></dt> <dd>Stop loading the current web page</dd>
|
||||
<dt><ex>:stopall</ex></dt> <dd>Stop loading all tab pages</dd>
|
||||
<dt><ex>:style</ex></dt> <dd>Style &dactyl.appname; and web sites</dd>
|
||||
<dt><ex>:style</ex></dt> <dd>Style &dactyl.appName; and web sites</dd>
|
||||
<dt><ex>:styledisable</ex></dt> <dd>Disable a user style sheet</dd>
|
||||
<dt><ex>:styleenable</ex></dt> <dd>Enable a user style sheet</dd>
|
||||
<dt><ex>:styletoggle</ex></dt> <dd>Toggle a user style sheet</dd>
|
||||
@@ -387,7 +387,7 @@ This file contains a list of all available commands, mappings and options.
|
||||
<dt><o>eventignore</o></dt> <dd>List of autocommand event names which should be ignored</dd>
|
||||
<dt><o>exrc</o></dt> <dd>Allow reading of an RC file in the current directory</dd>
|
||||
<dt><o>extendedhinttags</o></dt> <dd>XPath string of hintable elements activated by <k>;</k></dd>
|
||||
<dt><o>fileencoding</o></dt> <dd>Changes the character encoding that &dactyl.appname; uses to read and write files</dd>
|
||||
<dt><o>fileencoding</o></dt> <dd>Changes the character encoding that &dactyl.appName; uses to read and write files</dd>
|
||||
<dt><o>followhints</o></dt> <dd>Change the behaviour of <k name="Return"/> in Hints mode</dd>
|
||||
<dt><o>fullscreen</o></dt> <dd>Show the current window fullscreen</dd>
|
||||
<dt><o>guioptions</o></dt> <dd>Show or hide certain GUI elements like the menu or toolbar</dd>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="insert"
|
||||
title="&dactyl.appname; Insert Mode"
|
||||
title="&dactyl.appName; Insert Mode"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="Insert-mode Insert mode-insert">Insert mode</h1>
|
||||
|
||||
@@ -5,14 +5,14 @@
|
||||
|
||||
<document
|
||||
name="map"
|
||||
title="&dactyl.appname; Key Mappings"
|
||||
title="&dactyl.appName; Key Mappings"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="keyboard-shortcuts">Keyboard shortcuts and commands</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; provides a number of commands to change the
|
||||
&dactyl.appName; provides a number of commands to change the
|
||||
behavior of key presses. This can mean anything from
|
||||
automatically substituting one key for another or automatically
|
||||
replacing one typed word for another, to launching a dialog or
|
||||
@@ -22,7 +22,7 @@
|
||||
<h2 tag="key-mapping mapping map macro">Key mapping</h2>
|
||||
|
||||
<p>
|
||||
Key mappings are the most basic means &dactyl.appname; provides
|
||||
Key mappings are the most basic means &dactyl.appName; provides
|
||||
for altering the actions of key presses. Each key mapping is
|
||||
associated with a mode, such as <link topic="insert-mode">insert</link>,
|
||||
<link topic="normal-mode">normal</link>, or
|
||||
@@ -52,7 +52,7 @@
|
||||
<dt>n</dt> <dd>Normal mode: When browsing normally</dd>
|
||||
<dt>v</dt> <dd>Visual mode: When selecting text with the cursor keys</dd>
|
||||
<dt>i</dt> <dd>Insert mode: When interacting with text fields on a website</dd>
|
||||
<dt>c</dt> <dd>Command-line mode: When typing into the &dactyl.appname; command line</dd>
|
||||
<dt>c</dt> <dd>Command-line mode: When typing into the &dactyl.appName; command line</dd>
|
||||
</dl>
|
||||
|
||||
<p>
|
||||
@@ -381,7 +381,7 @@
|
||||
<h2 tag="abbreviations">Abbreviations</h2>
|
||||
|
||||
<p>
|
||||
In addition to basic mappings, &dactyl.appname; can also
|
||||
In addition to basic mappings, &dactyl.appName; can also
|
||||
automatically replace whole words after they've been typed.
|
||||
These shortcuts are known as abbreviations, and are most often
|
||||
useful for correcting spelling of commonly mistyped words, as
|
||||
@@ -624,7 +624,7 @@
|
||||
<dt>macro</dt> <dd>named macros</dd>
|
||||
<dt>mapping</dt> <dd>user mappings</dd>
|
||||
<dt>menu</dt> <dd>menu items</dd>
|
||||
<dt>option</dt> <dd>&dactyl.appname; options</dd>
|
||||
<dt>option</dt> <dd>&dactyl.appName; options</dd>
|
||||
<dt>preference</dt> <dd>&dactyl.host; preferences</dd>
|
||||
<dt>search</dt> <dd>search engines and keywords</dd>
|
||||
<dt>shellcmd</dt> <dd>shell commands</dd>
|
||||
|
||||
@@ -5,14 +5,14 @@
|
||||
|
||||
<document
|
||||
name="marks"
|
||||
title="&dactyl.appname; Marks"
|
||||
title="&dactyl.appName; Marks"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="marks">Marks</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; supports a number of different methods of
|
||||
&dactyl.appName; supports a number of different methods of
|
||||
marking your place, in order to easily return later,
|
||||
</p>
|
||||
|
||||
@@ -28,9 +28,9 @@
|
||||
|
||||
<p>
|
||||
Bookmarks are the most traditional kind of marks supported by
|
||||
&dactyl.appname;. They are accessible through &dactyl.host;'s
|
||||
&dactyl.appName;. They are accessible through &dactyl.host;'s
|
||||
bookmark menu, sidebar, and toolbar, in addition to its location
|
||||
bar completion system. &dactyl.appname; makes them accessible
|
||||
bar completion system. &dactyl.appName; makes them accessible
|
||||
not only via several commands and its completion system (see the
|
||||
<o>complete</o> option), but also displays a ❤ in the status bar
|
||||
when a bookmarked page is displayed.
|
||||
@@ -154,7 +154,7 @@
|
||||
<p>
|
||||
Though not traditionally considered a mark, history behaves very
|
||||
similarly to bookmarks both in &dactyl.host; and
|
||||
&dactyl.appname;. Every visited page is marked and weighted by
|
||||
&dactyl.appName;. Every visited page is marked and weighted by
|
||||
when and how often it is visited, and can be retrieved both in
|
||||
history list and location completions. Indeed, the ‘frecency’
|
||||
algorithm used to determine the results of location completions
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="message"
|
||||
title="&dactyl.appname; Messages"
|
||||
title="&dactyl.appName; Messages"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:dactyl="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
@@ -14,7 +14,7 @@
|
||||
<tags>message-history</tags>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; stores all info and error messages in a message
|
||||
&dactyl.appName; stores all info and error messages in a message
|
||||
history. The type of info messages output can be controlled by
|
||||
the <o>verbose</o> option. The maximum number of stored messages
|
||||
can be limited with the <o>messages</o> option.
|
||||
|
||||
@@ -14,14 +14,14 @@
|
||||
|
||||
<document
|
||||
name="options"
|
||||
title="&dactyl.appname; Options"
|
||||
title="&dactyl.appName; Options"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="options">Options</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; has a number of internal variables and switches which can be set to
|
||||
&dactyl.appName; has a number of internal variables and switches which can be set to
|
||||
achieve special effects. These options come in 8 forms:
|
||||
</p>
|
||||
|
||||
@@ -250,7 +250,7 @@
|
||||
<p>
|
||||
Show the &dactyl.host; preferences dialog. You can change the browser
|
||||
preferences from this dialog. Be aware that not all &dactyl.host;
|
||||
preferences work, because &dactyl.appname; overrides some key bindings and
|
||||
preferences work, because &dactyl.appName; overrides some key bindings and
|
||||
changes &dactyl.host;'s GUI.
|
||||
</p>
|
||||
</description>
|
||||
@@ -281,7 +281,7 @@
|
||||
</item>
|
||||
|
||||
<p tag="overridden-preferences">
|
||||
&dactyl.appname; needs to set several &dactyl.host; preferences at
|
||||
&dactyl.appName; needs to set several &dactyl.host; preferences at
|
||||
startup in order to function properly. If this is unacceptable,
|
||||
they can be changed in your RC file with the <ex>:set!</ex>
|
||||
command, but beware of unexpected behavior. The affected
|
||||
@@ -467,7 +467,7 @@
|
||||
</p>
|
||||
|
||||
<warning>
|
||||
&dactyl.appname; will not behave correctly if the editor forks its
|
||||
&dactyl.appName; will not behave correctly if the editor forks its
|
||||
own process, rather than blocking until editing is complete. Gvim
|
||||
invoked without the <em>-f</em> option is one such example.
|
||||
</warning>
|
||||
@@ -554,7 +554,7 @@
|
||||
<default>UTF-8</default>
|
||||
<description>
|
||||
<p>
|
||||
Changes the character encoding that &dactyl.appname; uses to read
|
||||
Changes the character encoding that &dactyl.appName; uses to read
|
||||
and write files.
|
||||
</p>
|
||||
</description>
|
||||
@@ -1090,11 +1090,11 @@
|
||||
|
||||
|
||||
<item>
|
||||
<tags>$&dactyl.idname;_RUNTIME</tags>
|
||||
<tags>$&dactyl.idName;_RUNTIME</tags>
|
||||
<tags>'rtp' 'runtimepath'</tags>
|
||||
<spec>'runtimepath' 'rtp'</spec>
|
||||
<type>stringlist</type>
|
||||
<default type="plain"><str>$&dactyl.idname;_RUNTIME</str> or
|
||||
<default type="plain"><str>$&dactyl.idName;_RUNTIME</str> or
|
||||
Unix, Mac: <str>~/.&dactyl.name;</str>
|
||||
Windows: <str>~/&dactyl.name;</str></default>
|
||||
<description>
|
||||
@@ -1117,8 +1117,8 @@
|
||||
</p>
|
||||
|
||||
<p>
|
||||
On startup, if the environment variable <em>$&dactyl.idname;_RUNTIME</em> does not
|
||||
exist, &dactyl.appname; will set it to match this value.
|
||||
On startup, if the environment variable <em>$&dactyl.idName;_RUNTIME</em> does not
|
||||
exist, &dactyl.appName; will set it to match this value.
|
||||
</p>
|
||||
</description>
|
||||
</item>
|
||||
@@ -1305,7 +1305,7 @@
|
||||
<tags>'titlestring'</tags>
|
||||
<spec>'titlestring'</spec>
|
||||
<type>string</type>
|
||||
<default>&dactyl.appname;</default>
|
||||
<default>&dactyl.appName;</default>
|
||||
<description>
|
||||
<p>
|
||||
Set the application name shown after the current page title in
|
||||
@@ -1353,7 +1353,7 @@
|
||||
<description>
|
||||
<p>
|
||||
Define which info messages are displayed. As the value increases,
|
||||
&dactyl.appname; will show more messages about its progress.
|
||||
&dactyl.appName; will show more messages about its progress.
|
||||
These can be viewed at any time with the <ex>:messages</ex>
|
||||
command. The highest useful value is 15, being the most verbose
|
||||
mode.
|
||||
|
||||
@@ -5,14 +5,14 @@
|
||||
|
||||
<document
|
||||
name="pattern"
|
||||
title="&dactyl.appname; Patterns"
|
||||
title="&dactyl.appName; Patterns"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="text-search-commands">Text search commands</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; provides a Vim-like incremental search interface to
|
||||
&dactyl.appName; provides a Vim-like incremental search interface to
|
||||
replace &dactyl.host;'s crippled Typeahead Find. Among other improvements,
|
||||
our search service:
|
||||
</p>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="print"
|
||||
title="&dactyl.appname; Printing"
|
||||
title="&dactyl.appName; Printing"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="printing">Printing</h1>
|
||||
|
||||
@@ -5,14 +5,14 @@
|
||||
|
||||
<document
|
||||
name="repeat"
|
||||
title="&dactyl.appname; Repeating Commands"
|
||||
title="&dactyl.appName; Repeating Commands"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="repeating">Repeating commands</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; can repeat commands in a number of ways, from repeating
|
||||
&dactyl.appName; can repeat commands in a number of ways, from repeating
|
||||
the last command, to recording and playing macros, to saving its state and
|
||||
executing scripts.
|
||||
</p>
|
||||
@@ -27,7 +27,7 @@
|
||||
<p>
|
||||
Repeat the last keyboard mapping <oa>count</oa> times. Note that,
|
||||
unlike in Vim, this does not apply solely to editing commands,
|
||||
mainly because &dactyl.appname; doesn't have them.
|
||||
mainly because &dactyl.appName; doesn't have them.
|
||||
</p>
|
||||
</description>
|
||||
</item>
|
||||
@@ -200,7 +200,7 @@
|
||||
<tt>&dactyl.name;rc</tt> file if <tt>&dactyl.name;rc</tt> uses commands or options
|
||||
which are defined by plugins. Additionally, this command allows
|
||||
newly installed plugins to be easily loaded without restarting
|
||||
&dactyl.appname;. See also <o>loadplugins</o>.
|
||||
&dactyl.appName;. See also <o>loadplugins</o>.
|
||||
</p>
|
||||
</description>
|
||||
</item>
|
||||
@@ -237,7 +237,7 @@
|
||||
<description>
|
||||
<p>
|
||||
Stop sourcing a script file. This can only be called from within a
|
||||
&dactyl.appname; script file.
|
||||
&dactyl.appName; script file.
|
||||
</p>
|
||||
</description>
|
||||
</item>
|
||||
|
||||
@@ -5,16 +5,16 @@
|
||||
|
||||
<document
|
||||
name="starting"
|
||||
title="&dactyl.appname; Starting"
|
||||
title="&dactyl.appName; Starting"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="starting">Starting &dactyl.appname;</h1>
|
||||
<h1 tag="starting">Starting &dactyl.appName;</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<h2 tag="startup-options">Command-line options</h2>
|
||||
|
||||
<p>
|
||||
Command-line options can be passed to &dactyl.appname; via the -&dactyl.name; &dactyl.host;
|
||||
Command-line options can be passed to &dactyl.appName; via the -&dactyl.name; &dactyl.host;
|
||||
option. These are passed as single string argument.
|
||||
E.g., &dactyl.hostbin; -&dactyl.name; <str>++cmd 'set exrc' +u 'tempRcFile' ++noplugin</str>
|
||||
</p>
|
||||
@@ -72,27 +72,27 @@
|
||||
|
||||
<h2 tag="initialization startup">Initialization</h2>
|
||||
|
||||
<p>At startup, &dactyl.appname; completes the following tasks in order. </p>
|
||||
<p>At startup, &dactyl.appName; completes the following tasks in order. </p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
<p>
|
||||
&dactyl.appname; first searches for user initialization commands in
|
||||
&dactyl.appName; first searches for user initialization commands in
|
||||
the following locations. The first of these to be found is executed,
|
||||
after which no further locations are searched.
|
||||
</p>
|
||||
|
||||
<ol>
|
||||
<li tag="$&dactyl.idname;_INIT">
|
||||
<em>$&dactyl.idname;_INIT</em>
|
||||
<li tag="$&dactyl.idName;_INIT">
|
||||
<em>$&dactyl.idName;_INIT</em>
|
||||
<strut/>
|
||||
May contain a single Ex command (e.g., "<ex>:source <a>file</a></ex>").
|
||||
</li>
|
||||
<li tag="$MY_&dactyl.idname;RC">
|
||||
<li tag="$MY_&dactyl.idName;RC">
|
||||
<em>~/_&dactyl.name;rc</em>
|
||||
<strut/>
|
||||
Windows only. If this file exists, its contents
|
||||
are executed and <em>$MY_&dactyl.idname;RC</em> set to its path.
|
||||
are executed and <em>$MY_&dactyl.idName;RC</em> set to its path.
|
||||
</li>
|
||||
<li>
|
||||
<em>~/.&dactyl.name;rc</em>
|
||||
@@ -137,7 +137,7 @@
|
||||
<ul>
|
||||
<li>On Unix and Mac, the environment variable <em>$HOME</em> is used.</li>
|
||||
<li>
|
||||
On Windows, &dactyl.appname; checks for the existence of
|
||||
On Windows, &dactyl.appName; checks for the existence of
|
||||
<em>%HOME%</em>, then <em>%USERPROFILE%</em>, and then
|
||||
<em>%HOMEDRIVE%%HOMEPATH%</em>. It uses the first one it
|
||||
finds.
|
||||
|
||||
@@ -5,17 +5,17 @@
|
||||
|
||||
<document
|
||||
name="styling"
|
||||
title="&dactyl.appname; Styling"
|
||||
title="&dactyl.appName; Styling"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="styling">Styling the GUI and web pages</h1>
|
||||
<toc start="2"/>
|
||||
|
||||
<p>
|
||||
&dactyl.appname; allows you to apply custom CSS styling to the web pages
|
||||
&dactyl.appName; allows you to apply custom CSS styling to the web pages
|
||||
you view as well as to the browser itself. Although it is possible to
|
||||
style any user interface element via the <ex>:style</ex> command, most
|
||||
&dactyl.appname; elements can be styled more easily by means of the
|
||||
&dactyl.appName; elements can be styled more easily by means of the
|
||||
more specialized <ex>:highlight</ex> command.
|
||||
</p>
|
||||
|
||||
@@ -53,7 +53,7 @@
|
||||
<p>Valid groups include:</p>
|
||||
|
||||
<dl>
|
||||
<dt>Bell</dt> <dd>&dactyl.appname;'s visual bell</dd>
|
||||
<dt>Bell</dt> <dd>&dactyl.appName;'s visual bell</dd>
|
||||
<dt>Boolean</dt> <dd>A JavaScript Boolean object</dd>
|
||||
<dt>CmdLine</dt> <dd>The command line</dd>
|
||||
<dt>CmdOutput</dt> <dd>The output of commands executed by <ex>:run</ex></dd>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="tabs"
|
||||
title="&dactyl.appname; Tabs"
|
||||
title="&dactyl.appName; Tabs"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1 tag="tabs buffers">Tabs and buffers</h1>
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
|
||||
<document
|
||||
name="various"
|
||||
title="&dactyl.appname; Other"
|
||||
title="&dactyl.appName; Other"
|
||||
xmlns="&xmlns.dactyl;"
|
||||
xmlns:html="&xmlns.html;">
|
||||
<h1>Other help</h1>
|
||||
@@ -124,7 +124,7 @@
|
||||
<spec>:ve<oa>rsion</oa><oa>!</oa></spec>
|
||||
<description>
|
||||
<p>
|
||||
Print &dactyl.appname; and &dactyl.host; version information. When
|
||||
Print &dactyl.appName; and &dactyl.host; version information. When
|
||||
<oa>!</oa> is provided, show the &dactyl.host; version page.
|
||||
</p>
|
||||
</description>
|
||||
@@ -133,17 +133,17 @@
|
||||
<h2 tag="privacy">Privacy and sensitive information</h2>
|
||||
|
||||
<p>
|
||||
Part of &dactyl.appname;'s user efficiency comes at the cost of storing a
|
||||
Part of &dactyl.appName;'s user efficiency comes at the cost of storing a
|
||||
lot of potentially private data, including <t>command-line</t> history, page
|
||||
marks, visited page history, and the like. Because we know that keeping a
|
||||
detailed trail of all of your activities isn't always welcome,
|
||||
&dactyl.appname; provides comprehensive facilities for erasing potentially
|
||||
&dactyl.appName; provides comprehensive facilities for erasing potentially
|
||||
sensitive data.
|
||||
</p>
|
||||
|
||||
<p tag="private-mode porn-mode">
|
||||
<strut/>
|
||||
&dactyl.appname; fully supports &dactyl.host;'s private browsing mode.
|
||||
&dactyl.appName; fully supports &dactyl.host;'s private browsing mode.
|
||||
When in private browsing mode, no data other than Bookmarks and QuickMarks
|
||||
are written to disk. Further, upon exiting private mode, all new data,
|
||||
including <t>command-line</t> history, local and URL marks, and macros,
|
||||
@@ -152,11 +152,11 @@
|
||||
|
||||
<p tag="sanitizing clearing-data">
|
||||
<strut/>
|
||||
In addition to private mode, &dactyl.appname; provides a comprehensive
|
||||
In addition to private mode, &dactyl.appName; provides a comprehensive
|
||||
facility for clearing any potentially sensitive data generated by either
|
||||
&dactyl.appname; or &dactyl.host;. It directly integrates with
|
||||
&dactyl.appName; or &dactyl.host;. It directly integrates with
|
||||
&dactyl.host;'s own sanitization facility, and so automatically clears any
|
||||
domain data and session history when requested. Further, &dactyl.appname;
|
||||
domain data and session history when requested. Further, &dactyl.appName;
|
||||
provides its own more granular sanitization facility, which allows, e.g.,
|
||||
clearing only the command-line and macro history for the past ten minutes.
|
||||
</p>
|
||||
|
||||
Reference in New Issue
Block a user