Bug 20813

Summary: use "|more" will lost one line of datas
Product: Base System Reporter: liber <liber>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description liber 2000-08-24 01:10:01 UTC 
If I use "|more" after some actions, those will lost one line of end of response.

How-To-Repeat: ls -l  (must more than your screen lines, any remember the last line)
ls -l |more (you would not see the last line you remember)

ps.use it at tty.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-24 09:55:10 UTC 
State Changed
From-To: open->feedback

Um, yes.  That's the way more works -- it's a pager.  You 
need to press the space bar to page down to the end of 
the output of the ls command. 

So were you just not paging down, or do you need to describe 
the problem in more detail? :-)
Comment 2 matt 2000-08-27 01:19:40 UTC 
I've seen the following variants:

1)  show lines 1-24 on screen 1, show lines 24-47 on screen 2, repeating
the last line from the first screen on the second.  This is the behaviour
that the user *wants* to experience, but isn't.  I usually see this when
I'm running an ansi session in a VT100 emulator.

2)  show lines 1-24 on screen 1, show lines 25-48 on screen 2.  This is
standard page-at-a-time with no repeats or loss.  This is what I normally
see in a properly set-upsession, either via telnet or at the console.

3)  show lines 1-24 on screen 1, show lines 26-49 on screen 2.  This
*skips* line 25, which I usually see on the console after setting VT100
emulation (when it should be ansi.)

The proper method is 2). Any other variants are a result of improper
terminal settings.

-- 
Matthew Emmerton      || matt@gsicomp.on.ca
GSI Computer Services || P: +1 (800) 217-5409
Technical Director    || F: +1 (519) 335-6584
Comment 3 Sheldon Hearn 2000-08-28 10:44:58 UTC 
All of the problems you describe sound like they're the result of
inappropriate terminal emulation.  I don't think this is something to be
resolved within more(1).

I still need feedback from the originator on whether or not he actually
understands what more(1) is supposed to do. :-)

Ciao,
Sheldon.
Comment 4 dirk freebsd_committer freebsd_triage 2000-11-10 13:39:04 UTC 
State Changed
From-To: feedback->closed

Feedback timeout...