Starting &dactyl.appName;
Command-line options
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; ++cmd 'set exrc' +u 'tempRcFile' ++noplugin
The -&dactyl.name;-remote command-line option can be used to
execute a single Ex command in an already running Pentadactyl instance.
-
+c
+c command
Execute a single Ex command after all initialization has been performed. See
initialization.
This option can be specified multiple times.
-
++cmd
++cmd command
Execute a single Ex command before any initialization has been performed. See
initialization.
This option can be specified multiple times.
-
+u
+u rcfile
The file rcfile is used for user initialization commands. If rcfile is
NORC then no startup initialization is performed except for the loading of
plugins, i.e., steps 1. and 2. in initialization are skipped. If rcfile
is NONE then plugin loading is also skipped.
-
++noplugin
++noplugin
Prevents plugin scripts from being loaded at startup. See loadplugins.
Initialization
At startup, &dactyl.appName; completes the following tasks in order.
-
&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.
-
$&dactyl.idName;_INIT
May contain a single Ex command (e.g., ":source file").
-
~/_&dactyl.name;rc
Windows only. If this file exists, its contents
are executed and $MY_&dactyl.idName;RC set to its path.
-
~/.&dactyl.name;rc
If this file exists, its contents are executed.
-
If exrc is set and the +u command-line option was not
specified, then any RC file in the current directory is also
sourced.
-
All directories in runtimepath are searched for a
‘plugins’ subdirectory and all yet unloaded plugins are loaded.
For each plugins directory, all *.{js,&dactyl.fileExt;}
files (including those in further subdirectories) are sourced
alphabetically. No plugins will be sourced if,
- loadplugins is unset,
- the ++noplugin command-line option was specified, or
- the +u=NONE command-line option was specified.
Any plugin which was already loaded (e.g., by an earlier
invocation of the :loadplugins command) will be skipped.
The user's home directory is determined as follows:
- On Unix and Mac, the environment variable $HOME is used.
-
On Windows, &dactyl.appName; checks for the existence of
%HOME%, then %USERPROFILE%, and then
%HOMEDRIVE%%HOMEPATH%. It uses the first one it
finds.
Saving settings
-
:mkp :mk&dactyl.name;rc
:mkpentadactylrc! file
Write current key mappings and changed options to file. If no
file is specified then ~/.&dactyl.name;rc is written unless this file
already exists. The special version :mk&dactyl.name;rc! will overwrite
file if it exists.
This behavior differs differs from that of Vim, which defaults to
writing the file in the current directory.
Restarting
-
:reh :rehash
:rehash arg …
Reload the &dactyl.appName; add-on, including all code, plugins,
and configuration. For users running directly from the development
repository, this is a good way to update to the latest version or
to test your changes.
Any arguments supplied are parsed as command-line arguments as
specified in startup-options.
Not all plugins are designed to cleanly un-apply during a rehash.
While official plugins are safe, beware of possible instability
if you rehash while running third-party plugins.
-
:res :restart
:restart
Force &dactyl.host; to restart. Useful when installing extensions.