| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rifle used to just fall back to using `xterm` when `flag t` was used and
`TERMCMD` didn't yield a valid command or the terminal emulator couldn't
be determined from the `TERM` variable.
Now when the need to fallback occurs rifle uses its own rules with a
custom mime type i.e. `ranger/x-terminal-emulator`. This way we can
provide a default sequence from rarer to more common terminal emulators
and users can change the fallback by editing `rifle.conf`
Fixes #1108
|
| | |
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Handle aliases for 'xterm', 'xterm-256color' by using 'xterm' if
$TERMCMD starts with 'xterm'.
If $TERMCMD in ['urxvt', 'rxvt-unicode'], use 'urxvt'.
If $TERMCMD in ['rxvt', 'rxvt-256color'], use 'rxvt' if found, otherwise
'urxvt'.
Tested 'termite (13-1)', 'terminology (1.1.1-1)', 'pantheon-terminal (0.4.3-2)'
and 'st (1:0.7.r38.g0ac685f-1)', these all use the -e flag.
Tested 'tilda (1.4.1-1)', which uses -c flag.
'tilda', 'pantheon-terminal', 'terminology' and 'termite' don't work
with the '/bin/sh --set' scheme. As a temp fix, get the application
name and argument from `command` and compose the `cmd` list from these.
See line 397--407 for details.
Let's forget about mac users, shall we?
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove some trailing whitespaces etc.
Another note: regarding iterm2 or some other terminals on mac,
it seems to be rather different to launch a new window in mac
than in linux. Some search suggests that you need to issue
open -a terminal -n
to open a new terminal window. So that would probably involve
other changes than simply getting a correct cmdflag.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Let's have the users report how they want shifting to work.
You can currently create tabs at negative indices so it feels wrong not
to be able to shift tabs there or have shifts of tabs at negative
indices have a weird result.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
offset will shift the tab number as seen
pos will shift the tab to the tav number given
preserves as much as possible the tab numbers
|
| | | | |
| | | | |
| | | | |
| | | | | |
shift selected tab right/left with ALT-p or ALT-o
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
offset will shift the tab number as seen
pos will shift the tab to the tav number given
preserves as much as possible the tab numbers
|
| | |/ / /
| |/| | |
| | | | |
| | | | | |
shift selected tab right/left with ALT-p or ALT-o
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
BRIGHT is additive, not idempotent like bold is. This caused what should
be bright text to be "unbrightened" again.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Brightness by itself is not always clear so in terminals that actually
support boldface it can help to differentiate.
Bright black can be hard to differentiate from white, this is the case
in kitty's default colorscheme. It's still better than the bold black
because while that was easily differentiated from white it was very hard
to see.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since most people use dark background terminals - yes, I'm assuming
because it's my preference - the black color for cut items is nearly
invisible the intention was for bold to be interpreted as bright but
that's a dirty dirty trick. Since dim white sounds like bright black
that's what we fall back to now for terminals that don't support BRIGHT
colors.
The solarized theme remains unchanged, so still uses bold, because it
looks like it knows what it's doing.
Fixes #1185
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Remove a setting that no longer exists from the man page.
Reformat the comment in `rc.conf`.
Use lower case `'none'` for consistency
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Update padding conditions to not show when draw_borders is set to
separators or none
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Allows drawing vertical separators between columns, borders around all
the columns, both of the two, or none
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`separators_only` argument
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| |_|_|/ / / / /
|/| | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If `selection == False` don't operate on the entire selection (the
marked files) but only on the file under the cursor.
Inconsistent, I noticed `move to=100 percentage=true` works as expected
but `move right=1 selection=false` doesn't. You need to pass `False`,
most other values test as `True` in python, so `true` works *but*
surprisingly imo, `false == True`.
Fixes #1233
|
|\ \ \ \ \ \ \ \ |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
I wanted to mention comic books explicitly because most people looking
for comic book previews probably won't look for archive previews.
|
| | | | | | | | | |
|