|
Grex > Info > #163: Why does "less" sometimes cut off the last line of what it displays? | |
|
| Author |
Message |
popcorn
|
|
Why does "less" sometimes cut off the last line of what it displays?
| 
Jul 7 05:07 UTC 1994 |
This item has been erased.
|
| 46 responses total. |
remmers
|
|
response 1 of 46:
|
Jul 7 09:38 UTC 1994 |
Hmm, doesn't happen to me. Do the folks who are complaining have
anything in common, such as using a particular terminal type, or
a particular communications program?
|
popcorn
|
|
response 2 of 46:
|
Jul 7 11:14 UTC 1994 |
This response has been erased.
|
carson
|
|
response 3 of 46:
|
Jul 7 16:08 UTC 1994 |
(I'm betting is has something to do with the number of rows on Grex vs.
the number of rows on home computer.)
|
remmers
|
|
response 4 of 46:
|
Jul 10 02:42 UTC 1994 |
Another question: Does the problem occur only with the "less" pager
but not with the "more" pager.
|
carson
|
|
response 5 of 46:
|
Jul 10 02:44 UTC 1994 |
(I'll vouch for the problem NOT occurring with the more pager, which is why
I prefer it.)
|
robh
|
|
response 6 of 46:
|
Jul 10 10:12 UTC 1994 |
I've never seen it happen with more.
|
remmers
|
|
response 7 of 46:
|
Jul 10 11:57 UTC 1994 |
But you have with "less", I take it?
|
popcorn
|
|
response 8 of 46:
|
Jul 10 13:12 UTC 1994 |
This response has been erased.
|
carson
|
|
response 9 of 46:
|
Jul 10 14:09 UTC 1994 |
(I've had it with "less"...)
(maybe I should phrase that another way. nah.)
|
nestene
|
|
response 10 of 46:
|
Jul 10 14:55 UTC 1994 |
I have sometimes had a problem with more deciding to clear the bottom
line of the screen both before and after it prints the first line of
the next screen, leaving a blank line in the middle of the text i'm viewing.
This behaviour convinced me to change to less.
|
remmers
|
|
response 11 of 46:
|
Jul 10 16:55 UTC 1994 |
Weird. I guess I'm the local termcap and terminal emulation guru
as much as anyone, so I'd be willing to try to trouble-shoot this.
But I haven't experienced the problem myself ("more" and "less" both
work correctly for me), so I need more data. If anyone has problems
with either "more" or "less", please describe (1) the symptoms,
(2) your terminal type on Grex (vt100, vt220, ansi, or whatever),
(3) what communication program you use, (4) what terminal emulation
your comm. program is set to. Thanks.
|
carson
|
|
response 12 of 46:
|
Jul 10 17:08 UTC 1994 |
(my problem with "less" is a result of my rows on Grex being a different
number than my rows on my comm. program. I know what the problem is, but I
don't feel like fixing it. I'd rather use more than less.)
(this is starting to feel surreal, let me tell you...)
|
remmers
|
|
response 13 of 46:
|
Jul 10 21:04 UTC 1994 |
If your comm. program is set for a smaller number of rows than Grex
thinks you have, that would account for the top on or more lines
scrolling off the top of the screen prematurely, but not for the
unwanted clearing of lines that other people seem to experience.
And it wouldn't account for a difference between "more" and "less"
either. Anybody else with pager problems care to relate their
symptoms.?
|
carson
|
|
response 14 of 46:
|
Jul 11 02:47 UTC 1994 |
(actually, my comm. program is set for a *larger* number of rows than Grex
thinks. This doesn't adversely affect the "more" pager for me, but it does
seem to throw off the "less" pager. If I set both equal, or at least within
2 of each other, I don't have any obvious problems.)
|
mju
|
|
response 15 of 46:
|
Jul 11 03:22 UTC 1994 |
This is because less uses the entire screen to scroll, but then moves
the cursor to what *it* thinks should be the last line before it prints the
prompt.
|
carson
|
|
response 16 of 46:
|
Jul 11 03:55 UTC 1994 |
(that makes sense.)
|
popcorn
|
|
response 17 of 46:
|
Jul 11 11:53 UTC 1994 |
This response has been erased.
|
remmers
|
|
response 18 of 46:
|
Jul 11 12:33 UTC 1994 |
#15 makes sense. Does Pattie's terminal screen have more than the
standard number of lines (24) for a VT100?
|
popcorn
|
|
response 19 of 46:
|
Jul 12 00:14 UTC 1994 |
This response has been erased.
|
popcorn
|
|
response 20 of 46:
|
Jul 13 12:56 UTC 1994 |
This response has been erased.
|
dam
|
|
response 21 of 46:
|
Jul 16 13:16 UTC 1994 |
well, I had troubles with less, specifically with my last line being
erased. I think I know what is wrong, I just never bothered to see
if I was correct. I'm using TELIX/vt102, I have the screen in 25 line
mode, and stty reports 24 lines, so in most cases, like more, I just get
to keep an extra line at the top. less, however, looks like it sends
the command to put the cursor at the 24th line from the top when getting
ready to continue, which of course is one too few lines for my screen.
|
remmers
|
|
response 22 of 46:
|
Jul 16 14:06 UTC 1994 |
Right, that's what happens, as mju pointed out earlier. "Less" moves
the cursor to what it *thinks* is the last line on the screen, clears
the line, which unfortunately contains text. The solution is to make
sure grex knows how many lines are on your display. The command
"stty rows 25" will do it if you have 25 lines.
|
tsty
|
|
response 23 of 46:
|
Jul 23 10:07 UTC 1994 |
How would you configure things if you WANTED, say, a 2-3 line overlap
from the last screen for continuity sake?
I have 35 rows, but configure for 32, vi doesn't mind either.
|
remmers
|
|
response 24 of 46:
|
Jul 23 14:26 UTC 1994 |
With "less", I think you'd use the -z option, which defines the
"window size". e.g. "less -z 20" would cause the screen to scroll
forward 20 lines when you go to the next screen, giving you 4 lines
of overlap on a 24-line display.
I believe "less" give you 1 or 2 lines of overlap by default.
|