about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Document ## convention and $$ sed rangetoonn2019-06-182-0/+5
| | |
| * | Add test_py targettoonn2019-06-181-0/+5
| | |
| * | Mention the test_py target in HACKING.mdtoonn2019-06-181-1/+3
| | |
| * | Document shellcheck in Makefile help and HACKING.mdtoonn2019-06-182-17/+18
| | |
| * | Add shellcheck to teststoonn2019-06-181-1/+5
| | | | | | | | | | | | Shellcheck is run for `scope.sh` after uncommenting all the code.
| * | Add a section for commands to avoid SC2034 warningstoonn2019-06-181-0/+3
| | | | | | | | | | | | | | | | | | | | | Shellcheck warns about unused variables, for good reason, but sometimes you legitimately want to include an unused variable in a script. Rather than ignore the warning completely I decided to circumvent the warning through the use of fluff (useless commands that "use" variables).
| * | Double up comment characters for commentstoonn2019-06-181-58/+59
| | | | | | | | | | | | | | | | | | To make it easy to automatically strip comments from sections of code I doubled up the comment characters for actual comments. This works for everything but the shebang line.
| * | Add double quotes SC2086toonn2019-06-181-2/+2
|/ /
* | Merge branch 'key_enter'toonn2019-06-181-0/+2
|\ \
| * | Treat KP_ENTER the same regardless of Num Lock statetoonn2019-05-281-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | KP_ENTER is only treated as newline by curses when Num Lock is on. This, like anything involving Num Lock, is confusing and has therefore been dealt with : ) Fixes #1568
* | | Merge branch 'tkunic-patch-1'toonn2019-06-182-7/+7
|\ \ \
| * | | Reword flag docs to mention both rc and rifle confstoonn2019-06-182-7/+7
| | | |
| * | | manpage: FLAGS are set in rc.conf, not rifle.conf.Toni Kunic2019-06-181-1/+1
|/ / /
* | | Merge pull request #1593 from Freso/add-gpicviewhut2019-06-171-0/+1
|\ \ \ | | | | | | | | Add gpicview to rifle.conf
| * | | Add gpicview to rifle.confFrederik “Freso” S. Olesen2019-06-151-0/+1
|/ / /
* | | Merge pull request #1567 from FichteForks/pr/safe-image-wdWojciech Siewierski2019-06-131-2/+4
|\ \ \ | | | | | | | | Open image displaying subprocesses in safe workdir
| * \ \ Merge branch 'master' into pr/safe-image-wdWojciech Siewierski2019-06-134-8/+19
| |\ \ \ | |/ / / |/| | |
* | | | Merge branch 'multipane_readme'toonn2019-06-061-0/+7
|\ \ \ \
| * | | | Align multi-pane screenshots side-by-sidetoonn2019-06-061-1/+4
| | | | |
| * | | | Add mc-like (two panes) screenshot to README.mdtoonn2019-06-061-1/+1
| | | | |
| * | | | Add a multi-pane screenshot to the READMEtoonn2019-05-211-0/+4
| | | | | | | | | | | | | | | | | | | | The more effectively to tempt `mc` users over to the dark side with : )
* | | | | Merge branch 'scope_svg'toonn2019-06-061-1/+1
|\ \ \ \ \
| * | | | | Some SVG have MIME type image/svgtoonn2019-06-061-1/+1
| | |_|/ / | |/| | | | | | | | | | | | | | | | | | | | | | | Scope now treats `image/svg` the same as `image/svg+xml` `image/svg` is not an official MIME type afaics *but* `file(1)` does sometimes determine it to be an svg's MIME type.
* | | | | Merge branch 'version_helper'toonn2019-06-061-1/+2
|\ \ \ \ \
| * | | | | Stop git errors before they reach usertoonn2019-06-061-1/+2
|/ / / / / | | | | | | | | | | | | | | | Fixes #1577
* | | | | Merge branch 'u91o-master'Toon Nolten2019-06-051-0/+1
|\ \ \ \ \
| * | | | | fix to call git describe in ranger's source directoryu91o2019-06-041-0/+1
|/ / / / /
* | | | | Merge branch 'py26_subprocess'toonn2019-05-291-4/+5
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Fix py2.6 incompatible use of subprocesstoonn2019-05-291-4/+5
|/ / / /
* | | | Atone for @Vifon's rash fixing of bugstoonn2019-05-281-3/+4
| | | | | | | | | | | | | | | | | | | | This required ritual sacrifice of many CPU cycles to appease the Almighty PyLint.
* | | | Replace the accidental str.join (as path.join) with os.path.joinWojciech Siewierski2019-05-271-1/+1
|/ / /
| * / Open image displaying subprocesses in safe workdirFichteFoll2019-05-241-2/+4
|/ / | | | | | | | | | | | | | | | | Otherwise, the current working directory of ranger would be used and could block operations like unmounting, because the handles would be kept alive by the previewer even when the directory isn't in use by ranger anymore. Fixes #1565.
* | Merge branch 'ape_media'toonn2019-05-211-0/+1
|\ \
| * | Add ape extension to mime.typestoonn2019-05-211-0/+1
|/ /
* | Merge branch 'flexible_highlight'toonn2019-05-203-42/+25
|\ \
| * | Give HIGHLIGHT_TABWIDTH some lovetoonn2019-05-193-7/+16
| | | | | | | | | | | | | | | | | | Same treatment as for `HIGHLIGHT_STYLE`. The default value can be overridden by either setting the environment variable or specifying `--replace-tabs=` in `HIGHLIGHT_OPTIONS`.
| * | Remove theme lists from syntax highlighting docstoonn2019-05-192-37/+11
| | | | | | | | | | | | | | | | | | | | | We mention commands to retrieve all the theme names so the explicit lists are redundant and will probably get out of date sooner rather than later and considering we all enjoy updating the docs *so much*, I figured we should just drop those : )
| * | Add missing documentation for syntax highlightingtoonn2019-05-172-11/+73
| | | | | | | | | | | | | | | `HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect ranger and should therefore be documented in the manual.
* | | Merge branch 'germainz-skip_ask'toonn2019-05-202-2/+5
|\ \ \
| * | | Do not include "ask" in open_with options (fixes #1047)GermainZ2018-10-152-2/+5
| | | |
* | | | Merge branch 'germainz-bulkrename_mkdir'toonn2019-05-191-6/+19
|\ \ \ \
| * | | | Updated the style to be more modern and pythonictoonn2019-05-191-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | Replaced the erroneous used of `extend` with `append`. It was working out by coincidence but probably making the `join` much less efficient.
| * | | | Make bulkrename create destination directories (fixes #963)GermainZ2018-10-161-3/+9
| |/ / /
* | | | Merge new and old %any documentationtoonn2019-05-182-65/+110
| | | | | | | | | | | | | | | | | | | | | | | | Some new docs were written up for the %any macro but they were in the wrong place. There were also some whitespace issues that snuck into the last commit that needed fixing up.
* | | | Add missing documentation for syntax highlightingtoonn2019-05-182-11/+73
| | | | | | | | | | | | | | | | | | | | `HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect ranger and should therefore be documented in the manual.
* | | | Rewriting some things and adding examplesStanislav Arnaudov2019-05-181-9/+22
| | | |
* | | | Documenting the use of <any>, %any and %any_pathStanislav Arnaudov2019-05-181-0/+14
| | | |
* | | | Merge pull request #1557 from toonn/flexible_highlightWojciech Siewierski2019-05-151-5/+8
|\ \ \ \ | | |/ / | |/| | Scope no longer interferes with users' configuration
| * | | Scope no longer interferes with users' configurationtoonn2019-05-151-5/+8
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our setup for syntax highlighting in `scope.sh` was actively preventing people's configuration for `highlight` from working. Now `HIGHLIGHT_OPTIONS` takes precendence over the default and over the `HIGHLIGHT_STYLE` environment variable. Users can specify `HIGHLIGHT_STYLE` or `PYGMENTIZE_STYLE` enviroment variables now to customize the syntax coloring theme without having to edit *and keep up to date* `scope.sh`. Fixes #1556
* | | Merge branch 'chmod_000'toonn2019-05-051-2/+3
|\ \ \
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2025-03-02 07:59:58 +0000