>Number:         2480
>Category:       bin
>Synopsis:       more -e option is poorly designed
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 29 04:35:04 1996
>Last-Modified:
>Originator:     David Eckhardt
>Organization:
Carnegie Mellon University, Department of CS
>Release:        1.1
>Environment:
	System: NetBSD piper.nectar.cs.cmu.edu 1.1 NetBSD 1.1 (GENERICOTHER) #1: Wed Mar 6 20:50:20 EST 1996 root@orion.fac.cs.cmu.edu:/usr/src/sys/arch/i386/compile/GENERICOTHER i386


>Description:
	The man page for more -e correctly writes:
     -e    Normally, if displaying a single file, more exits as soon as it
           reaches end-of-file.  The -e option tells more to exit if it reach-
           es end-of-file twice without an intervening operation.  If the file
           is shorter than a single screen more will exit at end-of-file re-
           gardless.
	This behavior is wrong when there are multiple files and one file
    is shorter than a single screen.  For example, imagine files a,b,c
    with b shorter than a screen, and a command line of "more a; more b;
	more c".  More will display a normally, throw b up on the screen,
	and then cover it up or scroll it away with c.
>How-To-Repeat:
	See above.
>Fix:
	make -e do the "right" thing regardless of file length.
>Audit-Trail:
>Unformatted: