There are several commands that can be used to configure Vifm (e.g.
:colorscheme), but, if you restart it, all
settings are reset to their previous values. To make changes permanent one
needs to put them into configuration file or ask Vifm to store them
automatically. Intent of this section is to describe things related to configuration.
Vifm follows the same configuration scheme as Vim and many other Unix applications use:
- main configuration file should be edited manually as it is only read by the application and is never modified by it;
- state of the application that is preserved across session is stored in separate file(s) and is not meant to be modified by a user.
For Vifm the first file is called
vifmrc (located at
~/.vifm/vifmrc by default) and the second one is
vifminfo (located at
vifmrc consists of regular commands that can be entered on the
vifminfo is usually written
automatically. Which settings are written and applied on startup depends on
'vifminfo' option. Instead of just overwriting all settings, Vifm
tries to merge previously stored state with the new one. Such strategy helps a
lot in managing multiple instances running at the same time. New settings have
higher priority than older ones, still Vifm tries to preserve as much of old
state as it can to do not forget history items or other settings that user might
want to reuse later.
Sometimes (e.g. before running external application that might affect
configuration of Vifm) it's useful to write
vifminfo file without
:write command is exactly for that.
Omitting writing of
vifminfo is written on exit, i.e.
is equal to
:wq, this means that requested changes are saved
automatically. Although it's quite convenient, sometimes one might want to drop
current runtime state in favor of previously stored one or state of another
instance. In such rare cases
:quit! command-line command or
ZQ normal mode shortcut can be used.
Moving configuration files
$VIFM environment variable.
Skipping load of configuration files
To ease diagnosing issues caused by configuration and provide a way to start
Vifm with sane defaults
--no-configs command-line option is
Passing it to Vifm blocks reading of both
vifminfo files. They can be read later via
command. You probably do not want to save
after running Vifm in this mode, so consider reading
related section of this page.