Fix an uncommon bug that would cause us to stop accepting input if the
user entered a command that filled exactly the remaining screen width.

Correctly backspace over number N that preceeds macros.

Allow excessive backspacing to correctly abort an input (most significantly
a search string input).

Thorough revamp of how input commands are processed. This allows customization
of user keys (documentation pending). The only key whose semantics have
changed is the capital 'N' key, which now perf

Thorough revamp of how input commands are processed. This allows customization
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?)

show more ...

$Id$ -> $FreeBSD$

- When trying to decide if $EDITOR == "vi", match against only the first
two characters of $EDITOR. This allows things like "vim" and "vi -G"
(although nvi would fail...oh well).

- Avoid certai

- When trying to decide if $EDITOR == "vi", match against only the first
two characters of $EDITOR. This allows things like "vim" and "vi -G"
(although nvi would fail...oh well).

- Avoid certain cases where the editor is passed an invalid line number.

show more ...

Grok gtags too.

General code cleanup [incomplete]. Make the arrow keys work.

$Id$ -> $FreeBSD$

[Whoops... used ci -m instead of -F on the last commit...]

MFC: misc incidental cleanup, gtags support, better line-number passing to
$EDITOR, working arrow keys, $Id$ to manpage

commit-notes

Fix bug from last commit: don't SEGV when reading as part of a pipe.

Prevent recursive help)elp)elping.

sprintf -> snprintf to avoid potential buffer overflow.

PR: 6907
Submitted by: Archie Cobbs <archie@whistle.com>

Make more not immediately exit on a short file, if the -e option is
given. This makes more -e basically usable at all when your termcap
entry supports an alternate screen buffer (like xterm-r6).

I

Make more not immediately exit on a short file, if the -e option is
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)

show more ...

MFC: doc fixes, enhancements to locate & more, new tail functionality.

YAMFC (rev 1.7, and 1.4 resp: don't exit immediately on short file if -e
is given, so alternate screen buffers can be used at all)

Fix a bug in a recent commit that broke more so that it
would no longer properly detect when "vi" was being called,
and thus would not call vi with the "+line#" argument.

Make more pass +linenumber to vi (and emacs), even if $EDITOR is used.
Closes PR#441, but with a more generic method.

Remove trailing whitespace.

Back out part of ctype fixes, unneded with new ctypoe

1) Make ctype-aware expect chars in range 0200-0204 treated
as controls in any case.
2) Fix bug with incorrect column position when standouts occurse
3) Fix bug when last standouted char cause cleari

1) Make ctype-aware expect chars in range 0200-0204 treated
as controls in any case.
2) Fix bug with incorrect column position when standouts occurse
3) Fix bug when last standouted char cause clearing next line
in standout

show more ...

BSD 4.4 Lite Usr.bin Sources

Initial revision