| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Fixes #1087
Useful on high-latency filesystems as it avoid calls to statvfs system
call which costs: (number of redraw) * latency.
|
| |/
|
|
|
|
|
|
|
|
|
| |
Changing the tmux window title to "ranger" was not guarded for the
presence of the tmux executable, this tripped up at least one user with
an `rc.conf` that still `set update_tmux_title true`.
While the behavior is *not-a-bug*, I expect most people'd rather have
the setting enabled by default since "python" is a less useful window
title.
Fix #1042
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Multiple users have complained about having problems with the way
`scope.sh` sourcing is handled:
* When running in clean mode
* When wanting to run with the default config
* When having non-default `$XDG_CONFIG_HOME`
Lays groundwork for further default setting handling in the future.
Fixes #840
Fixes #849
Closes #853
|
| |
|
|
| |
Fixes #782
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
The usage of file.basename could lead to some issues with :flat.
|
| |
|