Quitting Vifm

From Vifm Wiki
Revision as of 20:58, 11 September 2014 by Xaizek (talk | contribs) (→‎Preserving runtime state across sessions: Write introduction)
Jump to navigation Jump to search

Preserving runtime state across sessions

As described in Configuration model, Vifm can store some information between invocations in vifminfo file. What exactly is stored depends on the value of 'vifminfo' option. The option enumerates values elements of run-time state that can be saved on exit and restored on startup. It works this way:

  1. On exit Vifm stores all th is listed in vifminfo.
  2. On startup Vifm loads reads vifmrc, which normally contains set vifminfo=... and restores from vifminfo only items that correspond to that values.

By default only bookmarks are stored.

Below is the table of all possible values. Note those marked as obsolete, they might be removed in future versions (for a good reason: they don't fit into usual way configuration fails are used; it's better to put commands that correspond to this items into vifmrc).

TODO: table of things that can be stored (mark old-style things like commands and options as obsolete).

Possible members of vifminfo value
Value Default Obsolete Description

TODO: merging of state.

Remembering last visited directories of panes

TODO: how it affects starting Vifm without arguments.

Quitting Vifm started in file picker mode (e.g. from Vim plugin)

TODO: -f command-line argument.

TODO: running commands store selection and quit.

TODO: selection storage.

TODO: example for shell.

Updating shell directory after leaving Vifm

See How to set shell working directory after leaving Vifm.