Configuration model - Revision history

Xaizek: /* Configuration files */ Minor corrections

2022-06-11T08:20:56Z

Configuration files: Minor corrections

2022-03-27T08:43:21Z

Moving and finding configuration files

2022-03-27T08:42:20Z

Moving and finding configuration files

2022-03-27T08:37:55Z

Configuration files

2022-03-27T07:50:06Z

fix error

2017-11-09T14:38:57Z

Reloading configuration: Note that :restart doesn't rediscover configuration paths.

2017-11-09T14:15:58Z

Location of configuration files: "Parent directory of the executable" => "directory of the executable" (caused confusion)

2015-07-26T14:41:05Z

Location of configuration files: Expand TODO item, describe configuration directory discovery algorithm

2015-07-25T21:44:08Z

Location of configuration files: /etc is not mentioned anywhere, added

2014-10-01T20:53:54Z

Add location section for TODO

@@ Line 20: / Line 20: @@
 be set in this file via appropriate command-line commands.
-<code>vifminfo</code> is [[#Writing vifminfo manually|usually]] written
+<code>vifminfo.json</code> is [[#Writing vifminfo manually|usually]] written
-automatically.  Which settings are written and applied on startup depends on
+automatically.  Which settings are written and applied on future startups depends on
 <code>'vifminfo'</code> option.  Instead of just overwriting all settings, Vifm
 tries to merge previously stored state with the new one.  Such strategy helps a

@@ Line 87: / Line 87: @@
 * <code>$VIFM</code> points to main configuration directory (usually <code>~/.config/vifm/</code>);
-* <code>$MYVIFMRC</code> points to main configuration file (usually <code>$VIFM/vifmrc</code>).
+* <code>$MYVIFMRC</code> points to main configuration file (usually <code>~/.config/vifm/vifmrc</code>).
 These environment variables are valid inside Vifm and also can be used to

@@ Line 86: / Line 86: @@
 There are two environment variables that can be used in both cases:
-* <code>$VIFM</code> points to main configuration directory (usually <code>~/.vifm/</code>);
+* <code>$VIFM</code> points to main configuration directory (usually <code>~/.config/vifm/</code>);
-* <code>$MYVIFMRC</code> points to main configuration file (usually <code>~/.vifm/vifmrc</code>).
+* <code>$MYVIFMRC</code> points to main configuration file (usually <code>$VIFM/vifmrc</code>).
 These environment variables are valid inside Vifm and also can be used to

@@ Line 13: / Line 13: @@
 For Vifm the first file is called <code>vifmrc</code> (located at
-<code>~/.vifm/vifmrc</code> by default) and the second one is
+<code>~/.config/vifm/vifmrc</code> by default) and the second one is
-<code>vifminfo</code> (located at <code>~/.vifm/vifminfo</code>).
+<code>vifminfo</code> (located at <code>~/.config/vifm/vifminfo.json</code>).
 <code>vifmrc</code> consists of regular commands that can be entered on the

@@ Line 113: / Line 113: @@
 * one of configuration files is changed;
-* something made in current session is better to be undone, but restarting Vifm in inconvenient;
+* something made in current session is better to be undone, but restarting Vifm is inconvenient;
 * testing of something (e.g. new command) that is better to repeat in same environment multiple times.

@@ Line 116: / Line 116: @@
 * testing of something (e.g. new command) that is better to repeat in same environment multiple times.
-<code>:restart</code> command is there to make these usage scenarios possible.
+<code>:restart</code> command is there to make these usage scenarios possible. Note that it ''does '''not'''''
 It tries to repeat the same process that happens on startup, e.g.:

@@ Line 48: / Line 48: @@
 these places:
 # <code>$VIFM</code> variable;
-# Parent directory of the executable file (on Windows only);
+# Directory of the executable file (on Windows only);
 # <code>~/.vifm</code> directory;
 # <code>$APPDATA/Vifm</code> directory (on Windows only);
@@ Line 56: / Line 56: @@
 The configuration file itself is discovered this way on the last step:
 # <code>$MYVIFMRC</code> variable;
-# <code>vifmrc</code> in parent directory of the executable file (on Windows only);
+# <code>vifmrc</code> in the directory of the executable file (on Windows only);
 # <code>$VIFM/vifmrc</code> file.

@@ Line 31: / Line 31: @@
 ==== Location of configuration files ====
-''TODO: describe all possible variants (except envvars covered below) for different OSes''
+There are two locations: global one (<code>/etc/vifm</code>, available since 0.8)
-Support for /etc was implemented in 0.8.
+Path to global configuration is fixed at compile-time.  Local
 ==== Writing <code>vifminfo</code> manually ====

← Older revision		Revision as of 21:44, 25 July 2015
Line 32:		Line 32:

	''TODO: describe all possible variants (except envvars covered below) for different OSes''		''TODO: describe all possible variants (except envvars covered below) for different OSes''
		+
		+	Support for /etc was implemented in 0.8.

	==== Writing <code>vifminfo</code> manually ====		==== Writing <code>vifminfo</code> manually ====

@@ Line 28: / Line 28: @@
 state as it can to do not forget history items or other settings that user might
 want to reuse later.
 ==== Writing <code>vifminfo</code> manually ====