| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | | | | | | | | |
|
| | | | | | | | | | | | |
|
| | | | | | | | | | | | |
|
| | |\ \ \ \ \ \ \ \ \ \ |
|
| | | | | | | | | | | | | |
|
| | | |_|_|_|_|_|/ / / /
| | |/| | | | | | | | | |
|
| | | | | | | | | | | | |
|
| | | | | | | | | | | | |
|
| | | | | | | | | | | | |
|
| | |_|_|_|/ / / / / /
| |/| | | | | | | | | |
|
| | |_|/ / / / / / /
| |/| | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
Browser usage statistics are skewed *heavily* in favor of
chrome/chromium so it goes against our custom of ordering programs by
likelihood of preference, i.e., basically inverse frequency of usage.
|
| | |/ / / / / / /
| |/| | | | | | | |
|
| |\ \ \ \ \ \ \ \ |
|
| | | | | | | | | | |
|
| | | |_|/ / / / /
| | |/| | | | | |
| | | | | | | | |
| | | | | | | | | |
- also support wayland for flag t (opening in new terminal)
|
| | |_|_|_|_|_|/
| |/| | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`cunmap` definitely won't be missed because it was buggy. I'd expect the
other two to be even less missed.
I considered writing a decorator for deprecation because the code is
repetitive but imo it should be removed in the *next* version after
1.9.3 so it shouldn't matter much.
Fixes #1698
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
`cunmap` was broken and nobody noticed. It unmapped bindings in the
`browser` context, so it was basically an alias for `unmap`.
|
| |\ \ \ \ \ \ \ |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Provide a commented out alternative for the `<F8>` `:delete` key
binding.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Also add a generic rule that should serve a similar function to
`trash-cli`, i.e., move the files somewhere so they're marked for
deletion without actually deleting them. Should be fairly simple to
delete the trash by `rm -r`ing the trash directory.
|
| | | | | | | | | |
|
| | | |_|/ / / /
| | |/| | | | |
| | | | | | | |
| | | | | | | | |
Closes #1699.
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Previously it was hardcoded as 50, let's make it easy to change for
the user.
Improves upon #1705.
Related to #1704.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Macros are resolved for subcommands and the double resolution leads to
having to escape macros, which is bad UX. This does only show up in
select cases, such as with `%%space` at the end of a chained command.
Fixes #1640
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
50 characters seems to be the recommended length of the Git commit
messages.
|
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Fixes #1704.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| | | |
|