Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.sources.bugs
Subject: Re: less(1) bug (and fix)
Message-ID: <10@umcp-cs.UUCP>
Date: Sat, 1-Mar-86 22:50:17 EST
Article-I.D.: umcp-cs.10
Posted: Sat Mar  1 22:50:17 1986
Date-Received: Mon, 3-Mar-86 00:32:32 EST
References: <28800001@hpcvc0.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 26

In article <28800001@hpcvc0.UUCP> eric@hp-pcd.UUCP (Eric Gullerud) writes:

>I compiled the last posting of less(1), and found that (on HP terminals at
>least) when you scroll backwards and then quit or jump to a different
>location in the file your screen gets messed up because the contents of the
>screen BELOW the cursor weren't cleared.
>
>The fix is trivial... in screen.c, make the following change:
>
>223c223
>< 	sc_eol_clear = (dumb) ? NULL : tgetstr("ce", &sp);
>---
>> 	sc_eol_clear = (dumb) ? NULL : tgetstr("cd", &sp);

I am not sure what less uses `sc_eol_clear' for; but if the intention
is to clear to end of line, use `ce'; if it is to clear to the end
of the screen, use `cd'---but fake it if it is not available.
There is a termcap flag that indicates whether reverse scrolling
leaves text below the visible screen bottom.  It is `db'.  There
is a corresponding flag named `da', display retained above, that
indicates whether reverse scrolling may redisplay old scrolled
text.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu