On Wed, Mar 19, 2008 at 03:15:12AM +0000, Debian Bug Tracking System wrote:
>
> This is an automatic notification regarding your Bug report
> which was filed against the most package:
>
> #60673: most sets 24 lines on dumb terminal
>
> It has been closed by "Benj. Mako Hill" <[EMAIL PROTECTED]>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact "Benj. Mako Hill"
> <[EMAIL PROTECTED]> by
> replying to this email.
>
>
> --
> 60673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60673
> Debian Bug Tracking System
> Contact [EMAIL PROTECTED] with problems
> Date: Tue, 18 Mar 2008 23:07:31 -0400
> From: "Benj. Mako Hill" <[EMAIL PROTECTED]>
> Subject: closing this bug
> To: [EMAIL PROTECTED]
>
> After nearly 8 years, I believe this issue has been addressed. I'm
> closing this bug. Please reopen it if you care or notice an issue.
What makes you think it's been addressed? I had a lot of trouble
testing it now, since the terminal that had 25 lines when I reported
the bug failed a few years ago. But I tested it by falsely changing
the terminfo for my terminal to 25 lines instead of the 24 that it
actually has. "most" still sets the terminal for 24 lines and fails
to change it back to 25 lines when it's done. However I checked the
environment variable LINES and it's set to 25 likely not by "most" but
perhaps by the shell (a change in the past 8 years). This setting of
"LINES" provides a workaround for the problem.
So the problem is less severe than it previously was due to the
workaround, but "most" still fails to utilize the full number of lines
on the terminal. So perhaps it's now only "wishlist" item. I suggest
that the scrolling region specified by the terminfo (type "infocmp" on
the command line to see it: LINES#25 in my previous case) be used when
one starts most.
David Lawyer
>
> Regards,
> Mako
>
> --
> Benjamin Mako Hill
> [EMAIL PROTECTED]
> http://mako.cc/
>
> Creativity can be a social contribution, but only in so far
> as society is free to use the results. --GNU Manifesto
> Date: Fri, 17 Mar 2000 23:52:09 -0800
> From: David Lawyer <[EMAIL PROTECTED]>
> Subject: most sets 24 lines on dumb terminal
> To: [EMAIL PROTECTED]
>
> Package: most
> Version 4.9.0-1.1
>
> When started, "most" sends ESC [1;24r to a vt100 dumb terminal. This
> sets a 24-line scrolling region. My terminal has 25 lines and this
> fact is in the terminfo database. Yet "most" only uses 24 lines and
> when one exists "most" the scrolling region is still set to 24 lines.
> Then one runs other programs, some of them consult terminfo and see
> that the terminal is 25 lines. They get to line 25 by using direct
> cursor addressing and may leave the cursor on line 25 when they exit.
> Now the shell command line is 25 but it's outside the 24-line
> scrolling region so it doesn't scroll and the cursor is stuck in line
> 25 and will not exit it even if you hit <return>, etc.
>
> Now the main problem is that the user doesn't have a clue as to how this
> happened. There isn't any message telling him that the cursor is
> outside the scrolling region. In fact, there is no way to ask the
> terminal to tell you what scrolling region is set. It would seem that
> if "most" is sophisticated enough to use terminfo to set the scrolling
> region, it should be able to find the number of lines from terminfo
> also. Then it would set the scrolling region to this value.
>
> There is a fix for the problem and that's to set LINES=25 (as an
> environment variable) in etc. profile. It's very easy to fix but hard
> to figure out what's wrong. But I think that if "most" sets the
> scrolling region using an escape sequence that came from terminfo it
> should also be able to get the number of lines from the same terminfo.
>
> Note: My libc6 is 2.1.3-2 and slang1 is 1.3.9-1
> --
> David Lawyer
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
