summary refs log tree commit diff stats
path: root/doc/ranger.1
diff options
context:
space:
mode:
authorhut <hut@lavabit.com>2010-08-28 08:30:52 +0200
committerhut <hut@lavabit.com>2010-08-28 08:30:52 +0200
commita2853ab67f2e471d9a34b4c528db6ee2024ef874 (patch)
treecf2f7e32433cd49f592399e1624428e561a7c3e6 /doc/ranger.1
parent56f380c61f62a18b39375da7e7cd93d443be8aef (diff)
downloadranger-a2853ab67f2e471d9a34b4c528db6ee2024ef874.tar.gz
Changed default config dir to $XDG_CONFIG_HOME/ranger
Diffstat (limited to 'doc/ranger.1')
-rw-r--r--doc/ranger.19
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/ranger.1 b/doc/ranger.1
index 3db90285..fab42496 100644
--- a/doc/ranger.1
+++ b/doc/ranger.1
@@ -38,7 +38,8 @@ Return the exit code 1 if ranger is used to run a file, for example with
 `ranger --fail-unless-cd filename`.  This can be useful for scripts.
 .TP
 -r \fIdir\fR, --confdir=\fIdir\fR
-Define a different configuration directory.  The default is $HOME/.ranger.
+Define a different configuration directory.  The default is
+$XDG_CONFIG_HOME/ranger (which defaults to ~/.config/ranger)
 .TP
 -m \fIn\fR, --mode=\fIn\fR
 When a filename is supplied, make it run in mode \fIn\fR. Check the
@@ -177,17 +178,17 @@ of your parent shell after exiting ranger:
 
 ranger() {
     command ranger --fail-unless-cd $@ &&
-    cd "$(grep \\^\\' ~/.ranger/bookmarks | cut -b3-)"
+    cd "$(grep \\^\\' ~/.config/ranger/bookmarks | cut -b3-)"
 }
 .\"-----------------------------------------
 .SH CONFIGURATION
 The files in
 .B ranger/defaults/
 can be copied into your configuration directory (by default, this is
-$HOME/.ranger) and customized according to your wishes.  
+~/.config/ranger) and customized according to your wishes.
 Most files don't have to be copied completely though: Just define those
 settings you want to add or change and they will override the defauls.
-Colorschemes can be placed in $HOME/.ranger/colorschemes.
+Colorschemes can be placed in ~/.config/ranger/colorschemes.
 .P
 All configuration is done in Python.
 Each configuration file should contain sufficient documentation.
ame/arc/Readme?h=hlt&id=2e3b597fe85b654e82b891c22d50754fa5a26156'>^
f7c9c8f0 ^
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21