Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site utah-gr.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxm!mhuxj!houxm!whuxlm!harpo!decvax!genrad!panda!talcott!harvard!seismo!cmcl2!philabs!pwa-b!utah-gr!thomas
From: thomas@utah-gr.UUCP (Spencer W. Thomas)
Newsgroups: net.emacs
Subject: Re: wrap-long-lines meets next-page
Message-ID: <1330@utah-gr.UUCP>
Date: Mon, 4-Feb-85 23:16:59 EST
Article-I.D.: utah-gr.1330
Posted: Mon Feb  4 23:16:59 1985
Date-Received: Sat, 9-Feb-85 05:32:52 EST
References: <4563@ucbvax.ARPA>
Reply-To: thomas@utah-gr.UUCP (Spencer W. Thomas)
Distribution: net
Organization: Univ of Utah CS Dept
Lines: 18
Summary: 


In article <4563@ucbvax.ARPA> kupfer@ucbvax.ARPA (Mike Kupfer) writes:
>We're running (a somewhat hacked, I think) Gosmacs #85 here, and I've
>noticed the following problem: suppose you have wrap-long-lines set ON
>and n lines actually wrap around.  This means that your window is
>showing n fewer real lines of text than would happen if wrap-long-lines
>were OFF.  Now if you do a next-page, emacs doesn't account for this
>fact (that there are n fewer lines in the window) and moves forward n
>too many lines.

This is a "feature" of Gosling Emacs.  It is too lazy to determine which
lines are wrapped when doing the next-page function, so just moves
forward some number of lines and forces that line to the top of the
screen.

-- 
=Spencer
	({ihnp4,decvax}!utah-cs!thomas, thomas@utah-cs.ARPA)
		<<< "Ingvi is a louse!" >>>