calculation of line numbers) never existed and the two bugs that made me
think it existed have been fixed (see recent commits about this date to
linenum.c:r.1.3 and ch.c:r.1.8 fixing broken line-number buffering and
braindead algorithms respectively).
the docs on a couple other keys. While I'm here, document another ~3 bugs
that have been around for all eternity in the hope that I'll someday bother
to fix them.
of user keys (documentation pending). The only key whose semantics have
changed is the capital 'N' key, which now performs a repeat-search in the
opposite direction (just like in vi).
This commit is a little bulkier than what I had originally planned. I'm not
completely happy with the direction it went, but it's definately an
improvement, and the alternative is to continue becoming irrelevant compared
to GNU less. (Does anyone even _use_ /usr/bin/more these days?)
- Sort xrefs
- Be consistent with section names as outlines in mdoc(7).
- Other misc mdoc cleanup.
PR: doc/13144
Submitted by: Alexey M. Zelkin <phantom@cris.net>
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
given. This makes more -e basically usable at all when your termcap
entry supports an alternate screen buffer (like xterm-r6).
I wonder whether we should make more -e the default. Oure more seems
to be the only one on the world with this funny behaviour.
2.2 candidate
Submitted by: dawes@rf900.physics.usyd.edu.au (David Dawes)
