jaffe@caip.RUTGERS.EDU (Saul) (10/24/85)
I recently discovered a bug with the new scrolling capabilities in GNU Emacs. Apparently, the scrolling area is calculated and the appropriate string(s) is sent to the terminal but unfortunately the calculations are done wrong. The beginning location of the scrolling region is calculated correctly but the end location is some very large number (I've seen 705592 as an example). The end result proves disastrous for some devices like the vt100. The screen gets updated but the status line appears to move to the middle of the screen even though EMACS thinks it is still on the 23 line. If the terminal has display memory, the 23rd line is replaced by lines from the display memory. I haven't been able to find a solution to the problem but if anyone out there has a fix please let me know (rms????). I am getting a headache from plowing through the sources. My best guess is that some variable is getting clobbered or is not getting initialized by I can't figure out which one. Any help would be *greatly* appreciated. --
pajb@ulysses.UUCP (Paul Bennett) (10/25/85)
I, too, have problems with emacs use of the scrolling area. I
have version 16.56, (yes, I know its old), it seems to set the scroll
region to one more thannit needs to be, causing the mode line to move
as weel as the text. I fixed this by fiddling with the TERMCAP entry,
by making the usual offset character one less. i.e
cs=\Es%+ %+ :
goes to
cs=\Es%+ %+\037:
A hack, I know, but it seems to work.
--
Paul.
UUCP: {decvax,allegra,vax135,ucbvax}!ulysses!circe!pajb
DDD: (201) 582 7346
USPS: AT&T Bell Labs, Room 5E-103, Murray Hill, NJ 07974
.. I don't care WHO you are, you're not walking on the water while I'M fishing.