| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
|\ \ \
| | | |
| | | | |
Truncate the VCS commit message
|
| | | |
| | | |
| | | |
| | | |
| | | | |
50 characters seems to be the recommended length of the Git commit
messages.
|
|/ / /
| | |
| | |
| | | |
Fixes #1704.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Doctests are interfering with CI because curses can't find the terminfo
database. This'll require looking into but for now we'll run the
doctests seperately and expect failure. Same thing for pytests.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
By seperating the python 3.7 workflow we can keep an eye on changed
linting errors for the newer pylint. Without cancelling the actions for
our current setup.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Temporarily drop python 3.7 from the workflow because it's not
compatible with `pylint<2`.
|
|\ \ \ \ |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
One of the Debian patches patches our `ranger.desktop` to include
`Keywords`. I figure if we apply this, downstream need not bother and
many people can benefit.
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Document tab_shift keybindings
|
|/ / / /
| | | |
| | | |
| | | | |
Fixes #1592
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
I also added a utf8 encoding directive because pod2man complains
otherwise and I see no reason not to have a utf8 manpage.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
No longer will searching the docs say "Look elsewhere for the
information you were hoping to find." All these sections did was clutter
search results.
I took the liberty to reorder all the "taskview or pager" entries
because for some reason they weren't alphabetic.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The extra entries pointing from `copycmap` and co. to `copymap` only
contributed noise and confusion making their explanation harder to find.
This has summarily been dealt with using my exemplary SEO skills ; )
Fixes #1678
|
|/ / /
| | |
| | |
| | | |
Fixes #1678
|
|\ \ \
| |_|/
|/| | |
Document überzug preview method in the manpage
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #1453
|
| | | |
|
|/ / |
|
|\ \ |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
Quit closes a tab only when there is more than one tab;
otherwise, it quits the program.
Also fix a typo.
|
|\ \
| | |
| | | |
Add GitHub Actions ci
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \ |
|
|/ /
| |
| |
| |
| | |
Having the date in the manpage depend on a user's locale and their
timezone makes the format change depending on which user generates it.
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since GitHub’s Markdown doesn’t support resizing, we have to use html to
specify the width.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We’re getting the URL from ranger’s GitHub page, but it might be a better idea
to add it to the repo.
|
|\ \ \ \
| | | | |
| | | | | |
Improve the Dependencies section of the README
|
| | | | |
| | | | |
| | | | |
| | | | | |
Don't want people to think "More options" means settings.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Do not use article for ‘file’. Rephrase description for ‘python-bidi’.
Create sub-heading for optional dependencies. Mention ‘depencies’ in
the sub-heading, looks a tad barren otherwise. Change ‘General’ to
‘For general usage’. Change ‘for + noun’ to ‘to + verb’.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This section was incomplete because `scope.sh` has grown a lot.
Fixes #1611
|
|\ \ \ \
| |/ / /
|/| | | |
Make the wiki more visible
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|