| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
The `/media/$USER` locations aren't finalized yet so we're holding off
on that change.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Because of `udisks2` `/run/media/$USER` is becoming a common directory
for automounting, this adds a keybinding to go there (using the first
available letter in the path).
Similarly the binding for `/media` now points to `/media/$USER`, because
for example ubuntu adopted this new location.
I believe the `$USER` parts have to do with security, giving only the
user that mounted a filesystem access to it.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Check whether we're running in `tmux` by checking the existence of
`$TMUX` and only if so set the window title.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
|\ \ \ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Both rc.conf and commands.py are now additionally loaded from
`/etc/ranger` if they exist.
Fix #869
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #1128
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
os.getcwd() dereferences symlinks and it's usually undesirable.
Fixes #1105.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Python changed an error from `TypeError` to `ValueError` in version 3.5
now we catch both for backwards compatibility.
Relevant issue: https://bugs.python.org/issue22215
Fixes #990
Fixes #1045
Fixes #1079
Fixes #1082
Fixes #1086
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bash v3 doesn't support the `,,` syntax for lowercasing. This is
relevant on Mac OS which still comes with bash v3.2.
Using `:upper:` and `:lower:` with `tr` takes into account the locale so
this allows letters with diacritical marks in extensions.
This behavior may not be desirable.
Fixes #1072
|
|\ \ \ \ \ |
|
| | | | | | |
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I see no good reason why realpath was preferred there over abspath and
it clearly was breaking the process substitution (">(...)") by turning
for instance "/proc/self/fd/13" into "/proc/32444/fd/pipe:[4935093]",
the latter not being a valid file.
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Without this, there is no way to reload the “tagged” file. Being able to
reload it is nice, because you can tag paths using external utilities (e.g. a
feh action).
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
The metavar "PATH" is likely being confused with the environment
variable PATH. OUTFILE makes it clearer that the "PATH" in question is a
file.
|
| |/
|/|
| |
| |
| |
| |
| | |
For consistency with vim `gt` still means _go to the next tab_ the map
for _go to /tmp_ is now `gp` (first available letter in `/tmp`).
Fix #1040
|
| |
| |
| |
| |
| |
| |
| | |
If both `EDITOR` and `VISUAL` are unset, setting `VISUAL` because it's
technically the right thing to do and setting `EDITOR` for backwards
compatibility complicates the logic. `rifle` will now only do the
latter.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's 4 possible situation:
1. `VISUAL` set, `EDITOR` set
2. `VISUAL` set, `EDITOR` not set
3. `VISUAL` not set, `EDITOR` set
4. `VISUAL` not set, `EDITOR` not set
All but _No.2_ are already properly handled.
Behavior can differ depending on whether you have an old or a new
`rifle.conf` in cases _No.1_ (if the variables differ the new approach
prefers `VISUAL` instead of `EDITOR`) and _No.2_ (new approach will use
`VISUAL` whereas the old approach would've fallen back to _vim_).
_No.3_ is likely the most common case and works almost identically with
either approach.
_No.4_ still falls back to _vim_ as before.
Fix #1048
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When reading a file for which Ranger doesn't have permissions, Python3
throws an OSError. Python2 on the other hand throws a IOError, which
wasn't being caught and caused Ranger to crash. IOError was added to
catch statements for this reason.
|
| | | |
|
|\| | |
|
| |/
| |
| |
| | |
@nfnty: please document your settings in the man page too next time ;)
|
|/ |
|
|
|
|
|
|
| |
"Fuzzy" is the more applicable term here. "Smart" is often associated
with case sensitivity. So it would avoid confusion between
`set cd_tab_case smart` and `set cd_tab_smart true`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`VISUAL` is often misused to mean desktop GUI editor it's actual purpose
was to distinguish editors like `vi` (which is short for visual) from
editors like `ed` (which was probably short for editor), `EDITOR` is
actually intended to point to one of the latter.
Rifle still defaults to `vim` if both variables are undefined, even
with an old `rifle.conf` after trying to fall back on `EDITOR`.
For some better information on this see,
https://unix.stackexchange.com/a/334022
|
|
|
|
| |
Fixes #1035
|