| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
Fixes #1304
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
Upon further consideration we've reconsidered and decided to merge the
seperate title update settings.
|
| |\| |
|
| | |
| | |
| | |
| | | |
resolves #1637
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
`F<file_>` is rendered using underline in a man page, which makes the
underscore hard to see. So I switched the file name examples for `pp` to
use `C<file_>` which is rendered using "double quotation marks."
|
| | | | |
|
| |\ \ \
| | | |/
| | |/| |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
It allows you to specify your own function to generate the path for conflicting files.
|
| | |/
| |/|
| | |
| | | |
It allows you to specify 'overwrite', 'rename', or 'rename_ext' (=default) in case of a file name conflict. This obsoletes the overwrite parameter.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The man page was missing the various optional dependencies for previews.
I revised and then copied the list from the `README.md`.
Fixes #1781
|
|\ \ \ |
|
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | | |
Add to the cheatsheet the functionality of Space and some navigation
keys: Insert, Home, End, Page Up and Page Down.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously it was hardcoded as 50, let's make it easy to change for
the user.
Improves upon #1705.
Related to #1704.
|
|\ \ \ |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
|/ / /
| | |
| | |
| | | |
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
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #1453
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Quit closes a tab only when there is more than one tab;
otherwise, it quits the program.
Also fix a typo.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|/| |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
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`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We mention commands to retrieve all the theme names so the explicit
lists are redundant and will probably get out of date sooner rather than
later and considering we all enjoy updating the docs *so much*, I figured
we should just drop those : )
|
| | |
| | |
| | |
| | |
| | | |
`HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect
ranger and should therefore be documented in the manual.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Some new docs were written up for the %any macro but they were in the
wrong place. There were also some whitespace issues that snuck into the
last commit that needed fixing up.
|
| | |
| | |
| | |
| | |
| | | |
`HIGHLIGHT_STYLE`, `HIGHLIGHT_OPTIONS` and `PYGMENTIZE_STYLE` affect
ranger and should therefore be documented in the manual.
|