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)
This commit is contained in:
parent
095777c6a0
commit
984e3edbe2
@ -174,7 +174,7 @@ prompt()
|
||||
repaint();
|
||||
|
||||
/* if no -e flag and we've hit EOF on the last file, quit. */
|
||||
if ((!quit_at_eof || short_file) && hit_eof && curr_ac + 1 >= ac)
|
||||
if (!quit_at_eof && hit_eof && curr_ac + 1 >= ac)
|
||||
quit();
|
||||
|
||||
/* select the proper prompt and display it. */
|
||||
|
@ -79,9 +79,6 @@ exits as soon as it reaches end-of-file. The
|
||||
.Fl e
|
||||
option tells more to
|
||||
exit if it reaches end-of-file twice without an intervening operation.
|
||||
If the file is shorter than a single screen
|
||||
.Nm more
|
||||
will exit at end-of-file regardless.
|
||||
.It Fl i
|
||||
The
|
||||
.Fl i
|
||||
|
Loading…
Reference in New Issue
Block a user