about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | Merge pull request #1710 from Vifon/vifon/trash-cliWojciech Siewierski2019-10-023-1/+71
|\ \ \ \ \ | |_|_|_|/ |/| | | | Add a trash-cli support to the default rifle.conf
| * | | | Merge pull request #3 from toonn/rifle-trashWojciech Siewierski2019-10-023-1/+62
| |\ \ \ \ | | | | | | | | | | | | Rifle trash
| | * | | | Simplify alternative trash rifle ruletoonn2019-10-021-1/+1
| | | | | |
| | * | | | Remove MC-like F9 binding for :trashtoonn2019-10-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Provide a commented out alternative for the `<F8>` `:delete` key binding.
| | * | | | Add bindings for :trash commandtoonn2019-10-021-0/+2
| | | | | |
| | * | | | Add :trash command relying on rifle's trash labeltoonn2019-10-021-0/+58
| | | | | |
| | * | | | Add "trash" label to rifle rules for conveniencetoonn2019-10-021-1/+2
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | | Reword the rifle.conf commentsWojciech Siewierski2019-10-021-3/+8
| | | | |
| * | | | Offer trash-put as an option in rifleWojciech Siewierski2019-10-011-1/+5
|/ / / / | | | | | | | | | | | | Closes #1699.
| * | | Reword the vcs_msg_length docsWojciech Siewierski2019-10-022-2/+4
| | | |
| * | | Add a configurable VCS max message lengthWojciech Siewierski2019-10-016-2/+20
|/ / / | | | | | | | | | | | | | | | | | | | | | Previously it was hardcoded as 50, let's make it easy to change for the user. Improves upon #1705. Related to #1704.
* | | Merge pull request #1705 from Vifon/vcs-truncateToon Nolten2019-10-011-1/+1
|\ \ \ | | | | | | | | Truncate the VCS commit message
| * | | Change the commit msg truncation pointWojciech Siewierski2019-10-011-1/+1
| | | | | | | | | | | | | | | | | | | | 50 characters seems to be the recommended length of the Git commit messages.
| * | | gui.widgets.statusbar: Truncate the VCS commit messageWojciech Siewierski2019-10-011-1/+1
|/ / / | | | | | | | | | Fixes #1704.
* | | Merge branch 'gh-actions'toonn2019-09-263-3/+63
|\ \ \
| * | | Seperate doctests and pyteststoonn2019-09-242-2/+32
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Segregate python 3.7 workflowtoonn2019-09-181-0/+30
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Drop py3.7toonn2019-09-181-1/+1
| | | | | | | | | | | | | | | | | | | | Temporarily drop python 3.7 from the workflow because it's not compatible with `pylint<2`.
* | | | Merge branch 'dotdesktop'toonn2019-09-241-0/+1
|\ \ \ \
| * | | | Add Launcher to keywords because of rifletoonn2019-09-241-1/+1
| | | | |
| * | | | Apply debian patch 0004 desktop entry lacks keywordstoonn2019-09-241-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | Merge pull request #1689 from toonn/doc-shift-tabsWojciech Siewierski2019-09-242-1/+8
|\ \ \ \ \ | |/ / / / |/| | | | Document tab_shift keybindings
| * | | | Document tab_shift keybindingstoonn2019-09-242-1/+8
|/ / / / | | | | | | | | | | | | Fixes #1592
* | | | Merge branch 'doc-copymap'toonn2019-09-242-76/+57
|\ \ \ \ | |/ / / |/| | |
| * | | Add multiple section headings for command variationstoonn2019-09-232-8/+50
| | | | | | | | | | | | | | | | | | | | I also added a utf8 encoding directive because pod2man complains otherwise and I see no reason not to have a utf8 manpage.
| * | | Give cmap and cunmap and friends similar treatmentToon Nolten2019-09-202-53/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | Remove redundant copymap sectionstoonn2019-09-182-25/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | Add example to copymap manpage entrytoonn2019-09-182-3/+5
|/ / / | | | | | | | | | Fixes #1678
* | | Merge pull request #1697 from toonn/doc-ueberzugToon Nolten2019-09-172-34/+53
|\ \ \ | |_|/ |/| | Document überzug preview method in the manpage
| * | Capitalize LinuxToon Nolten2019-09-172-13/+13
| | |
| * | Document überzug preview method in the manpagetoonn2019-09-172-0/+19
| | | | | | | | | | | | Fixes #1453
| * | Reorder preview method sections alphabeticallytoonn2019-09-172-32/+32
| | |
| * | Manpage typo for kitty preview methodtoonn2019-09-172-13/+13
|/ /
* | Merge branch 'vifon-verbose-delete'toonn2019-09-101-1/+1
|\ \
| * | core.actions: Log which files were deletedWojciech Siewierski2019-09-101-1/+1
|/ /
* | Correct the description of 'quit'Benno Schulenberg2019-09-102-4/+4
| | | | | | | | | | | | | | Quit closes a tab only when there is more than one tab; otherwise, it quits the program. Also fix a typo.
* | Merge pull request #1687 from toonn/gh-actionsWojciech Siewierski2019-09-033-1/+52
|\ \ | | | | | | Add GitHub Actions ci
| * | Add GitHub Actions citoonn2019-09-033-1/+52
|/ / | | | | | | | | | | | | | | | | | | 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.
* | Merge branch 'iso-date'toonn2019-09-011-2/+2
|\ \
| * | Switch manpage date from locale dependent to ISO UTCtoonn2019-09-011-2/+2
|/ / | | | | | | | | 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.
* | Merge PR #1649Wojciech Siewierski2019-08-187-11/+52
|\ \
| * | Regenerate the manpagesWojciech Siewierski2019-08-182-20/+24
| | |
| * | Drop truth values; rename warning settingToon Nolten2019-08-186-18/+32
| | |
| * | Warn when nesting rangertoonn2019-08-034-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Merge branch 'add-logo' of https://github.com/Zaeph/rangerhut2019-08-061-0/+2
|\ \ \
| * | | Resize logoLeo Vivier2019-08-041-1/+1
| | | | | | | | | | | | | | | | | | | | Since GitHub’s Markdown doesn’t support resizing, we have to use html to specify the width.
| * | | Add logo to README.mdLeo Vivier2019-08-041-0/+2
| | | | | | | | | | | | | | | | | | | | We’re getting the URL from ranger’s GitHub page, but it might be a better idea to add it to the repo.
* | | | Merge pull request #1657 from toonn/readme-dependenciesWojciech Siewierski2019-08-051-11/+21
|\ \ \ \ | | | | | | | | | | Improve the Dependencies section of the README
| * | | | Change phrasing to avoid confusiontoonn2019-08-051-1/+1
| | | | | | | | | | | | | | | | | | | | Don't want people to think "More options" means settings.
| * | | | Further README improvementsLeo Vivier2019-08-051-6/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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’.