Message-ID: <bnews.allegra.1002>
Newsgroups: net.emacs
Path: utzoo!decvax!harpo!eagle!allegra!phr
X-Path: utzoo!decvax!harpo!eagle!allegra!phr
From: allegra!phr
Date: Tue Mar  8 07:48:40 1983
Subject: re: gripe about the display
Posted: Thu Mar  3 13:02:37 1983
Received: Tue Mar  8 07:48:40 1983

What's worse, Emacs counts folded lines as still taking one line on the
screen.  If lots of lines on the screen are more than 80 chars long,
Emacs still thinks there are 24 lines on the current page.  After you
hit forward-page, the lines off the bottom of the previous screenful
are skipped over, and you never get to see them.

Message-ID: <bnews.cbosgd.3223>
Newsgroups: net.emacs
Path: utzoo!decvax!harpo!npoiv!hou5f!hou5b!hou5c!hou5e!hou5a!hou5d!houxz!
houxi!houxa!houxm!npois!cbosgd!mark
X-Path: utzoo!decvax!harpo!npoiv!hou5f!hou5b!hou5c!hou5e!hou5a!hou5d!houxz!
houxi!houxa!houxm!npois!cbosgd!mark
From: cbosgd!mark
Date: Tue Mar  8 03:37:45 1983
Subject: Re: A gripe about the display
References: <bnews.526@sri-arpa.UUCP>
Posted: Fri Mar  4 13:29:22 1983
Received: Tue Mar  8 03:37:45 1983

	Where would you put the cursor when at the end of such a line?

You could do what vi does - put the cursor at the beginning of the next
line, without doing the insert line unless an 81st character is typed.
This is ambiguous but I've never seen anybody complain about it in vi,
it never seems to cause any confusion.

James has solved the "does this terminal have automatic margins" problem
by just not using the last column.  It turns out that, as long as you don't
use the last column of the bottom line (because that can cause scrolling),
there are no real problems with using all 80 (or whatever) columns.  You
do have to know which of three kinds of terminals you have:
(1) automatic margin: cursor goes to next row, first column.
(2) non-auto margin: cursor hammers on right margin (stays put)
(3) eat-newline: (vt100 and concept) terminal goes into weird state so that
    if crlf follows, it eats the automatic margin, otherwise it generates one.
    This is handled by outputting an extra crlf after the 80th char.

This info is present in termcap and terminfo, so EMACS should have no trouble
accessing it.  However, note that even if you only write characters in the
first 79 columns, there is no problem with putting the cursor in column 80,
solving the first problem above.  Also note that, for all practical purposes,
a text editor user won't care whether there are 78 or 80 columns available,
unless editing card images or some screen layout that is 80 columns wide.

Message-ID: <bnews.rocheste.889>
Newsgroups: net.emacs
Path: utzoo!decvax!microsof!uw-beave!cornell!vax135!ariel!hou5f!npoiv!
harpo!seismo!rocheste!dean
X-Path: utzoo!decvax!microsof!uw-beave!cornell!vax135!ariel!hou5f!npoiv!
harpo!seismo!rocheste!dean
From: rocheste!dean
Date: Wed Mar  9 03:37:24 1983
Subject: Re: A gripe about the display
Posted: Fri Mar  4 15:29:56 1983
Received: Wed Mar  9 03:37:24 1983

From: Mike.Dean
My big complaint about how Gosling's emacs handles long lines is
with regard to its redisplay logic.  When inserting characters into
a line, the redisplay correctly uses the insert mode of my terminal
(a heath19) until it begins to wrap around.  At this point, it
starts repainting each of the characters until it gets to the last
"continuation line".  On a dialup this can get quite annoying.

	Mike Dean
	rochester!dean