| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\|
| |
| |
| |
| | |
Conflicts:
doc/ranger.1
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
this indicates that ranger should not be used as a file launcher
anymore, since it now ships with the standalone program `rifle'.
|
| | |
|
| |
| |
| |
| |
| | |
this avoids garbled output for a pager that doesn't pass through ansi
codes to the terminal
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Again, use rifle as a file launcher instead
|
| |
| |
| |
| | |
Instead of launching ranger for opening files, simply use rifle.
|
| |
| |
| |
| |
| | |
The command :narrow has few use cases, which will be served by a system
that'll be implemented at a later point.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
The variables vcs_backend_git, vcs_backend_hg and vcs_backend_bzr have three
possible values: disabled, local (only local info) and enabled (local and remote
info).
|
| | |
|
| | |
|
|\| |
|