| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\ |
|
| | |
|
|\ \
| | |
| | | |
Add geeqie image viewer to the default `rifle.conf`.
|
|/ / |
|
|/
|
|
|
|
|
| |
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.
|
|
|
|
| |
(Thanks to Klemens Nanni for pointing it out)
|
|
|
|
|
|
|
| |
This ensures compatibility with non-GNU implementations like OpenBSD's
find(1).
-and is already implied by juxtaposition, thus remove it.
|
|\
| |
| | |
Solve map conflict for `gt`.
|
|/
|
|
|
|
|
| |
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
|
|\
| |
| | |
Make new `rifle` behavior backwards compatible.
|
| |\
| |/
|/| |
|
| |
| |
| |
| | |
Signed-off-by: ael-code
|
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
|\| | | | |
|
| | | | | |
|
| | | | | |
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
@hut: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@nfnty: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@Klinkenstecker: please document your settings in the man page next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
@kattrali: please add a distinct entry in the man page for every setting
you add
|
| | | | |
| | | | |
| | | | |
| | | | | |
@hut: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@jgreco: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@randynobx: 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`.
|