summary refs log tree commit diff stats
path: root/ranger
Commit message (Collapse)AuthorAgeFilesLines
* ext.rifle: Additional Check for mime type with mimetype commandMichael Ilsaas2018-04-271-0/+5
|
* Fix typo for pdf in rifle.confRoman Pearah2018-03-291-1/+1
| | | | Fixes #1128
* rc.conf: Use smartcase in :find and :filterWojciech Siewierski2018-03-281-2/+2
|
* Avoid calling os.getcwd()Wojciech Siewierski2018-03-071-5/+5
| | | | | | os.getcwd() dereferences symlinks and it's usually undesirable. Fixes #1105.
* Cleanup lists and generatorsWojciech Siewierski2018-03-041-3/+3
|
* Fix the coding styleWojciech Siewierski2018-03-042-5/+7
|
* Add the 'hint_collapse_threshold' that controls when the submaps are collapsedWojciech Siewierski2018-03-043-5/+21
|
* Show the full keybindings in the key hintsWojciech Siewierski2018-03-041-10/+43
|
* Clarify the comment and fix the urltoonn2018-02-241-1/+2
|
* Catch the right errors in addstrtoonn2018-02-241-1/+2
| | | | | | | | | | | | 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
* Please do not turn off your phone while upgrading...Wojciech Siewierski2018-02-222-2/+2
|
* Make scope.sh backwards compatible with bash v3toonn2018-02-161-1/+1
| | | | | | | | | | 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
* Merge branch 'tag_add_parameters' of github:NoSuck/rangertoonn2018-02-141-4/+4
|\
| * Fully encompass tag_toggleThe Flying Rapist2018-02-091-4/+4
| |
* | Add geeqie image viewer supportAndrew Rabert2018-02-111-0/+1
| |
* | Allow to use >(...) in Bash for --choosedir & its friendsWojciech Siewierski2018-02-111-1/+1
|/ | | | | | | 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.
* Reload tags on resetThe Flying Rapist2018-02-091-0/+1
| | | | | | 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).
* change PATH to OUTFILE to avoid confusionAlexander Blesius2018-02-061-6/+6
| | | | | | The metavar "PATH" is likely being confused with the environment variable PATH. OUTFILE makes it clearer that the "PATH" in question is a file.
* Solve map conflict for `gt`.toonn2018-02-011-1/+1
| | | | | | | 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
* Simplify backwards compatibility logic for VISUAL.toonn2018-01-311-9/+2
| | | | | | | 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.
* Make new `rifle` behavior backwards compatible.toonn2018-01-311-4/+9
| | | | | | | | | | | | | | | | | | | | 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
* change branch label back to "master"hut2018-01-281-1/+1
|
* Merge branch 'master' into v1.9.0hut2018-01-284-7/+14
|\
| * ext.img_display: cleaner catching of OSError/IOErrorhut2018-01-282-26/+7
| |
| * Merge remote-tracking branch 'chronzerg/master'hut2018-01-284-2/+28
| |\
| | * Added more IOError checks for Python2.Jon Anderson2018-01-272-0/+24
| | |
| | * Added except catching for Python2.Jon Anderson2018-01-272-2/+4
| | | | | | | | | | | | | | | | | | | | | 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.
* | | core.main: rearranged command line itemshut2018-01-281-2/+2
| | |
* | | Merge branch 'master' into v1.9.0hut2018-01-281-1/+2
|\| |
| * | manpage: document `vcs_backend_svn` settinghut2018-01-281-1/+2
| |/ | | | | | | @nfnty: please document your settings in the man page too next time ;)
* / WIP of version bumphut2018-01-252-3/+3
|/
* Renamed `cd_tab_smart` to `cd_tab_fuzzy`hut2018-01-253-8/+9
| | | | | | "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`.
* config.commands: clearer error messagehut2018-01-241-1/+2
|
* Prefer VISUAL to EDITORtoonn2018-01-232-4/+6
| | | | | | | | | | | | | `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
* widgets.view_miller: fix broken pager after changing view modehut2018-01-231-4/+4
| | | | Fixes #1035
* Updated rifle.conf moved google-chrome below chromium.Peter Stevenson2018-01-111-1/+1
| | | Prioritise chromium as I think most Linux users would prefer that as default over google-chrome.
* Fix ranger not opening in chrome, chromium on Ubuntu.Peter Stevenson2018-01-071-24/+26
| | | | Added `has google-chrome` and `has chromium-browser` then adjusted the spacing to adjust for new longer `has chromium-browser` line. This allows Ubuntu users to open in google-chrome and chromium-browser packages.
* Merge branch 'column_ratios_tab_completion' of https://github.com/Vifon/rangerhut2018-01-071-5/+14
|\
| * config.commands: Coding style fixWojciech Siewierski2018-01-041-5/+7
| |
| * config.commands: :set tab completion refactoringWojciech Siewierski2018-01-031-7/+12
| |
| * config.commands: Make the column_ratios setting completion actually usefulWojciech Siewierski2018-01-031-0/+2
| | | | | | | | A stringified list, as before, cannot be used in the :set command.
* | Fix spectre vulnerabilityhut2018-01-041-1/+0
|/
* config.commands: fix pylint directivehut2017-12-251-1/+1
|
* config.commands: import ranger for eval(). Fixes #1007hut2017-12-251-0/+2
|
* data/scope.sh: added --force to "highlight" command, fixes #988hut2017-12-201-1/+1
|
* Merge branch 'master' of https://github.com/jgreco/rangerhut2017-12-203-4/+12
|\
| * Add config opts for iTerm2 font size (for preview)john2017-10-223-4/+12
| | | | | | | | | | | | | | | | Add two config options "iterm2_font_width" and "iterm2_font_height" that override the default values of _minimum_font_width and _minimum_font_height in ITerm2ImageDisplayer. The default values may cause preview distortion if set too high (Issue #499) or result in the preview being smaller than necessary if set too low.
* | fix drasill's commit so it passes CIhut2017-12-201-3/+5
| |
* | Merge branch 'terminology' of https://github.com/drasill/rangerhut2017-12-202-0/+58
|\ \
| * | Implement the terminology-based image previewsChristophe Badoit2017-05-182-0/+58
| | |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-27 16:51:45 +0000