| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Rewrote the epub clauses to avoid overlap warnings `SC2221/SC2222`,
users could've potentially been confused if they uncommented both
Calibre and epub-thumbnailer clauses and didn't see epub-thumbnailer
previews.
|
| |
|
|
|
|
|
|
| |
Hid an `echo $VAR` in a comment to get rid of the unused variable
warning, that's now been replaced with a shellcheck directives suited to
the purpose.
|
|
|
|
| |
The comment was confusing because `make` swallowed the `$`
|
|
|
|
|
|
|
|
| |
It's easier to keep the test and test_py targets synchronized by having
the former depend on the latter.
Changed the wording of the test_py success message to be less
suspenseful.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Shellcheck is run for `scope.sh` after uncommenting all the code.
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
| |
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.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | | |
Add gpicview to rifle.conf
|
|/ / |
|
|\ \
| | |
| | | |
Open image displaying subprocesses in safe workdir
|
| |\ \
| |/ /
|/| | |
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
The more effectively to tempt `mc` users over to the dark side with : )
|
|\ \ \ \ |
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | | |
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.
|
|\ \ \ \ |
|
|/ / / /
| | | |
| | | |
| | | | |
Fixes #1577
|
|\ \ \ \ |
|
|/ / / / |
|
|\ \ \ \
| |/ / /
|/| | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | | |
This required ritual sacrifice of many CPU cycles to appease the
Almighty PyLint.
|
|/ / |
|
|/
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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`.
|
| |
| |
| |
| |
| |
| |
| | |
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 : )
|
| |
| |
| |
| |
| | |
`HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect
ranger and should therefore be documented in the manual.
|
|\ \ |
|
| | | |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Replaced the erroneous used of `extend` with `append`. It was working
out by coincidence but probably making the `join` much less efficient.
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | | |
`HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect
ranger and should therefore be documented in the manual.
|