summary refs log tree commit diff stats
path: root/examples
diff options
context:
space:
mode:
authortoonn <toonn@toonn.io>2019-08-03 00:29:10 +0200
committertoonn <toonn@toonn.io>2019-08-03 00:29:10 +0200
commit498ac4ffa7b90d385de6078a9162606a6bc524c3 (patch)
treedbd31fc46f55caafe5670944fb7aebe661a79a5d /examples
parent6fee63a8d7f91a91ffa2b785e67f4d418055bd98 (diff)
downloadranger-498ac4ffa7b90d385de6078a9162606a6bc524c3.tar.gz
Warn when nesting ranger
Users frequently request that launching ranger in a subshell started
from ranger (using `S`) instead exits the subshell so they end up in
their original ranger instance without nesting, which is rarely useful.
This isn't possible because a process can't easily kill its parent
shell.

To at least avoid such confusion we warn about nesting by default.
A new setting `nested_ranger_warning` is added to `rc.conf`. The warning
can be either disabled or the severity increased so the message is more
visible.

Fixes #1645
Diffstat (limited to 'examples')
-rw-r--r--examples/rc_emacs.conf5
1 files changed, 5 insertions, 0 deletions
diff --git a/examples/rc_emacs.conf b/examples/rc_emacs.conf
index 0462282e..a2e81892 100644
--- a/examples/rc_emacs.conf
+++ b/examples/rc_emacs.conf
@@ -206,6 +206,11 @@ set idle_delay 2000
 # check all directories above the current one as well?
 set metadata_deep_search false
 
+# Warn at startup if RANGER_LEVEL env var is greater than 0, in other words
+# give a warning when you nest ranger in a subshell started by ranger.
+# Special value "bad" makes the warning more visible.
+set nested_ranger_warning true
+
 # ===================================================================
 # == Local Options
 # ===================================================================