| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Quit closes a tab only when there is more than one tab;
otherwise, it quits the program.
Also fix a typo.
|
|
|
|
|
|
|
|
|
|
| |
Run our python tests and shellcheck in seperate workflows only when
relevant files are changed, respectively python files or `scope.sh`.
This tests with one extra version of python, 3.7.
GitHub's version of shellcheck seems to be missing a few flags. So we
download the latest stable version, 0.7.0 currently.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Users frequently request that launching ranger in a subshell started
from ranger (using `S`) instead exits the subshell so they end up in
their original ranger instance without nesting, which is rarely useful.
This isn't possible because a process can't easily kill its parent
shell.
To at least avoid such confusion we warn about nesting by default.
A new setting `nested_ranger_warning` is added to `rc.conf`. The warning
can be either disabled or the severity increased so the message is more
visible.
Fixes #1645
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
| |
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
|
| | |
|
|\ \ |
|
| |\ \ |
|
| | |/
| | |
| | |
| | |
| | |
| | | |
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`.
|
|\ \ |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Replaced the erroneous used of `extend` with `append`. It was working
out by coincidence but probably making the `join` much less efficient.
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
`not self.quantifier` excluded `0`, which is a perfectly valid
quantifier for `chmod`.
|
| | | |
|
|\ \ \
| |/ /
|/| |
| | | |
joelostblom-human-linemodes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's already a `human_readable` for size in `ranger/ext`, I figure we
might as well add the new helper there, make it easily accessible in
other code.
Did some renaming, no need to drop the `readable` part to shorten the
names. Similarly I changed one of the mappings to be more intuitive.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|