starting.html

Vimperator does not yet read any command-line options. When it does, they will be documented here.

Initialization

startup initialization

At startup, Vimperator completes the following tasks in order.

  1. Vimperator can perform user initialization commands. When one of the following is successfully located, it is executed, and no further locations are tried.

    1. $VIMPERATOR_INIT $VIMPERATOR_INIT — May contain a single Ex command (e.g., ":source {file}").

    2. ~/vimperatorrc — Windows only. If this file exists, its contents are executed and $MY_VIMPERATORRC_ set to its path.

    3. ~/.vimperatorrc — If this file exists, its contents are executed.

  2. If 'exrc' is set, then any RC file in the current directory is also sourced.

  3. All directories in 'runtimepath' are searched for a "plugin" subdirectory and all yet unloaded plugins are loaded. For each plugin directory, all *.{js,vimp} files (including those in further subdirectories) are sourced alphabetically. No plugins will be sourced if 'noloadplugins' is set. Any particular plugin will not be loaded if it has already been loaded (e.g., by an earlier :loadplugins command).

The user's ~ (i.e., "home") directory is determined as follows:

Saving settings

save-settings

:mkv :mkvimperatorrc

:mkv[imperatorrc][!] [file]

Write current key mappings and changed options to [file]. If no [file] is specified then ~/.vimperatorrc is written unless this file already exists. The special version :mkvimperatorrc! will overwrite [file] if it exists.

Warning: this differs from Vim's behavior which defaults to writing the file in the current directory.

Restarting

restarting

:res :restart

:res[tart]

Force the browser to restart. Useful when installing extensions.