Before this change, if you had a search hit inside inverse video text
with a non standard color, search hits in there would be invisible.
With this change in place, we now force the search hits highlights to
use the default colors, making them visible in this case.
This could sometimes be a problem when searching riff highlighted git
diffs:
https://github.com/walles/riff
Before this change, we just didn't highlight in this case.
With this change in place, we now fall back on the default dark theme
when background color detection fails.
Fixes <https://github.com/walles/moar/issues/202>.
I don't understand how this happens, but:
* It's uncommon
* It's been reported once during startup
* I'm assuming this is a race condition during startup
* Let's just treat the scroll position as zero if unset
Then let's cross our fingers and hope we don't crash anywhere else in
this situation.
Fixes: https://github.com/walles/moar/issues/198
When entering `0` as the go-to-line number.
Reported here:
https://github.com/walles/moar/issues/199
Note that this just prevents the crash, but it doesn't make sudo work
any better so the ticket should still be open.
By default. Press left arrow to get them back. Or use start moar with
--no-linenumbers=false.
`man` starts by checking the terminal width, and then formats man pages
to fit that width.
Then, if moar adds line numbers, the rightmost part of the man page
will be shifted out of view.
So we try to detect showing man pages, and in that case disable line
numbers so that the rightmost part of the page is visible by default.
Fixes#200.
These files are archives, which moar is not designed to view. However,
for tar files containing text, decompressing them before showing them
will make at least text files in the archive readable.
Fixes#194.
With this change in place you can invoke moar like this:
moar file1 file2 file3 | wc -l
Note that I believe this is a corner case, and I will on purpose leave
this undocumented.
Fixes#187