about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
| | | * | Change rifle fallback mechanism for flag ttoonn2018-06-232-9/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | | * | remove term=term.lower()guangzhi2018-05-191-7/+5
| | | | |
| | | * | Merge branch 'master' into flagtXunius2018-05-1916-40/+59
| | | |\ \
| | | * \ \ Merge branch 'master' into flagtXunius2018-05-1521-68/+255
| | | |\ \ \
| | | * | | | more terminals tested for fix of issue #1108guangzhi2018-03-161-20/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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?
| | | * | | | Correct some formatting in fix of issue #1108.guangzhi2018-03-131-10/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * | | | re-organize block regarding flag t issue #1108guangzhi2018-03-131-21/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | | * | | | run test and fix some formattingguangzhi2018-03-111-9/+9
| | | | | | |
| | | * | | | Attempt to fix issue #1108 flag t problemguangzhi2018-03-111-7/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | * | | | | Merge branch 'dbosst-master'toonn2018-09-082-0/+49
| | |\ \ \ \ \
| | | * | | | | Removed ghost of function definitiontoonn2018-08-231-53/+0
| | | | | | | |
| | | * | | | | Remove limit and change pos to totoonn2018-08-221-11/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * | | | | use offset and pos to shift tabs:dbosst2018-08-221-16/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | | * | | | | Added: shift tabs right/leftdbosst2018-08-221-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | shift selected tab right/left with ALT-p or ALT-o
| | | * | | | | Merge branch 'master' into masterdbosst2018-03-281-2/+2
| | | |\ \ \ \ \
| | | * | | | | | use offset and pos to shift tabs:dbosst2018-03-282-18/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | | * | | | | | Added: shift tabs right/leftdbosst2018-03-272-0/+30
| | | | |/ / / / | | | |/| | | | | | | | | | | | | | | | | | | | shift selected tab right/left with ALT-p or ALT-o
| | * | | | | | Merge branch 'boldisnotbright'toonn2018-09-083-5/+29
| | |\ \ \ \ \ \
| | | * | | | | | Fix unbrightened selectionToon Nolten2018-09-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | BRIGHT is additive, not idempotent like bold is. This caused what should be bright text to be "unbrightened" again.
| | | * | | | | | Restore the use of the bold attributetoonn2018-09-072-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * | | | | | In terminals devoid of color cut items were invisibletoonn2018-09-073-16/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | * | | | | | | Merge branch 'squigglezworth-master'toonn2018-09-086-56/+92
| | |\ \ \ \ \ \ \
| | | * | | | | | | Fix documentationtoonn2018-09-084-21/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove a setting that no longer exists from the man page. Reformat the comment in `rc.conf`. Use lower case `'none'` for consistency
| | | * | | | | | | Fix commit 520e76esquigz2018-01-051-2/+1
| | | | | | | | | |
| | | * | | | | | | Another pylint fix (2 spaces before in-line comment)squigz2018-01-051-1/+1
| | | | | | | | | |
| | | * | | | | | | Merge branch 'master' into mastersquigglezworth2018-01-051-1/+0
| | | |\ \ \ \ \ \ \
| | | * | | | | | | | Disable pylint too-many-branches for _draw_borderssquigz2018-01-051-0/+1
| | | | | | | | | | |
| | | * | | | | | | | Further draw_borders refactoring, "both" isn't now a distinct stateWojciech Siewierski2018-01-051-9/+17
| | | | | | | | | | |
| | | * | | | | | | | Clean up the draw_borders codeWojciech Siewierski2018-01-051-12/+11
| | | | | | | | | | |
| | | * | | | | | | | draw_borders: treat true as both for backwards compatibilitysquigz2018-01-041-1/+1
| | | | | | | | | | |
| | | * | | | | | | | remove unnecessary checkssquigz2018-01-041-2/+2
| | | | | | | | | | |
| | | * | | | | | | | Reduce calls to string.lower()squigz2018-01-041-5/+4
| | | | | | | | | | |
| | | * | | | | | | | Update manpage section on draw_borderssquigz2018-01-042-5/+17
| | | | | | | | | | |
| | | * | | | | | | | Fix rc.confsquigz2018-01-041-1/+1
| | | | | | | | | | |
| | | * | | | | | | | Use True/False instead of 1/0squigz2018-01-041-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Update padding conditions to not show when draw_borders is set to separators or none
| | | * | | | | | | | Remove draw_separators from ALLOWED_SETTINGSsquigz2018-01-041-1/+0
| | | | | | | | | | |
| | | * | | | | | | | Changes draw_borders setting to a stringsquigz2018-01-043-38/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allows drawing vertical separators between columns, borders around all the columns, both of the two, or none
| | | * | | | | | | | Remove _draw_separators and integrate with _draw_borders with the ↵squigz2018-01-041-64/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `separators_only` argument
| | | * | | | | | | | Fix draw_separators setting in rc.confsquigz2018-01-041-1/+1
| | | | | | | | | | |
| | | * | | | | | | | Update manpage with 'draw_separator' settingsquigz2018-01-043-2/+9
| | | | | | | | | | |
| | | * | | | | | | | Add 'draw_separators' option to rc.confsquigz2018-01-041-0/+3
| | | | | | | | | | |
| | | * | | | | | | | Add option to draw separators between columns instead of drawing boxessquigz2018-01-032-0/+47
| | | | | | | | | | |
| | * | | | | | | | | Merge pull request #1228 from natemaia/patch-4Wojciech Siewierski2018-09-071-0/+70
| | |\ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Update plugin_pmount.py
| | | * \ \ \ \ \ \ \ \ Merge branch 'master' into patch-4Nathaniel2018-09-0519-37/+586
| | | |\ \ \ \ \ \ \ \ \
| | | * | | | | | | | | | Remove extra pipe in subprocess call, rename plugin and add originalnatemaia2018-09-052-47/+89
| | | | | | | | | | | | |
| | | * | | | | | | | | | 2 lines around function definitionNathaniel2018-07-071-0/+1
| | | | | | | | | | | | |
| | | * | | | | | | | | | import order and break long linesNathaniel2018-07-071-8/+12
| | | | | | | | | | | | |
| | | * | | | | | | | | | Indentation and whitespace cleanupNathaniel2018-07-071-12/+8
| | | | | | | | | | | | |
| | | * | | | | | | | | | Update plugin_pmount.pyNathaniel2018-07-071-20/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the pmount plugin uses static device letters and partition numbers. this change uses present devices and partitions. - Changes the binds to remove the need for uppercase device letters, if a device has no partitions <alt><m or M><device letter> mounts/unmounts the device. - With only one partition the same binds will handle it instead of the whole device. - With greater than one partitions, map <alt><m or M><device letter><partition number> for each. This is still not fully functional, devices not present when ranger is started *(usb drives)* won't have a map created unless ranger is restarted :| ... Is there a simple way to have ranger 'reload' this plugin, or use a different hook, etc.?
| | * | | | | | | | | | | Merge branch 'moveright'toonn2018-09-071-2/+5
| | |\ \ \ \ \ \ \ \ \ \ \ | | | |_|_|_|_|/ / / / / / | | |/| | | | | | | | | |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-11 14:54:16 +0000