| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes made to rifle.py:
* get `term` from `os.environ['TERMCMD']`, if failed, use `TERM`
* if `term` not found in executables, fall back to `xterm`
* choose `cmdflag` according to `term`, currently have 3 choices:
* `-e`: tested terminals + versions:
* xterm (331-1)
* urxvt (9.22)
* lxterminal (0.3.1-1)
* konsole (17.12.2-1)
* lilyterm (0.9.9.2-2)
* cool-retro-term (1.0.1-1)
* `-x`:
* xfce4-terminal (0.8.7.1-1)
* mate-terminal (1.20.0-1)
* terminator (1.91-5)
* gnome-terminal (3.26.2)
* `--`:
* gnome-terminal (3.26.2)
* terminals that are found not working when tested:
* pantheon-terminal (0.4.3-2): not -e or -x or --execute
(people using elementary probably won't use ranger anyway).
* terminology (1.1.1-1): not -e or -x
* tilda (1.4.1-1): with -c tilda opens but not entering editor
* kitty (0.8.0-1): don't think this has the functionality
* terminals haven't tested:
* st
* termite (having conflicts on my system)
* iterm2
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
issue #1108: Rifle's flag t only works with urxvt (and xterm) (because
who cares about standards?). Urxvt passes any arguments after -e
verbatim, most other terminals consume them as arguments. Some
terminals use -e, others use -x.
Fix: in rifle.py, if $TERMCMD is set to gnome-terminal, xfce4-terminal
etc., give either -e or -x that pairs with the terminal. If $TERMCMD not
found in executables, fall back to xterm and -e.
|
|
|
|
|
|
| |
os.getcwd() dereferences symlinks and it's usually undesirable.
Fixes #1105.
|
| |
|
|\
| |
| | |
Show the full keybindings in the key hints
|
| | |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Catch the right errors in addstr
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Make scope.sh backwards compatible with bash v3
|
|/
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| | |
|
|\ \
| | |
| | | |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | |\ |
|