Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!linus!decvax!ucbvax!ucdavis!lll-crg!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.emacs
Subject: Re: 79-character screen
Message-ID: <1804@umcp-cs.UUCP>
Date: Thu, 10-Oct-85 20:51:46 EDT
Article-I.D.: umcp-cs.1804
Posted: Thu Oct 10 20:51:46 1985
Date-Received: Sat, 12-Oct-85 08:06:57 EDT
References: <70@druhi.UUCP> <336@uwvax.UUCP> <17@mit-eddie.UUCP> <1776@umcp-cs.UUCP> <39@mit-eddie.UUCP>
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 26

In article <39@mit-eddie.UUCP> barmar@mit-eddie.UUCP (Barry Margolin) writes:
>... I am not familiar with the internals of Gosling Emacs, only
>Multics Emacs.  Its redisplay-line routine is independent of the
>actual screen line, so it only has the global line length variable
>to deal width.

The display code in Gosling Emacs is pretty similar:  I was proposing
that the line redisplay be made dependent on the actual screen line.
Basically, there would be a per-terminal flag saying `I cannot handle
the last character of the last line, so do not ask me to'; and making
the display code honor that would not be hard.

[me]
>>---but there is no real incentive since most of our local terminals
>>are automatically set to non-wrap mode while running Emacs.

>How do you deal with the different ways that terminals handle the
>no-wrap case, with respect to relative cursor motion after entering a
>character in the 80th column?

On a per-terminal basis, with hardwired drivers.  I know, it is not
wonderful.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu