From 004badd136850ec48533eb3591b841d4ee38e156 Mon Sep 17 00:00:00 2001 From: nfnty Date: Thu, 16 Feb 2017 05:33:50 +0100 Subject: doc: man: Clarify config sourcing --- doc/ranger.pod | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) (limited to 'doc/ranger.pod') diff --git a/doc/ranger.pod b/doc/ranger.pod index 8b02ee63..bb30fab3 100644 --- a/doc/ranger.pod +++ b/doc/ranger.pod @@ -1406,18 +1406,15 @@ out the tag argument, all tagged files are unmarked. ranger reads several configuration files which are located in F<$HOME/.config/ranger> or F<$XDG_CONFIG_HOME/ranger> if $XDG_CONFIG_HOME is defined. You can use the --copy-config option to obtain the default -configuration files. Each of the files contains further documentation. - -You don't need to copy the whole file though, most configuration files are -overlaid on top of the defaults (F, F) or can be -sub-classed (F). - -That being said, the user configuration files F and F are -loaded only after ranger loads the default configuration files. This may lead -to some confusing situations, for example when a key is being bound despite the -corresponding line being removed from the user's copy of the configuration -file. This behavior may be disabled with an environment variable (see also: -B). +configuration files. The files contain further documentation. + +F, F and F do not need to be copied fully +as they will only be adding to the default configuration files except if explicitly +overridden. This may lead to some confusing situations, for example when a key is +being bound despite the corresponding line being removed from the user's copy of +the configuration file. This behavior may be disabled with an environment +variable (see also: B). Note: All other configuration files only +read from one source; i.e. default OR user, not both. When starting ranger with the B<--clean> option, it will not access or create any of these files. -- cgit 1.4.1-2-gfad0