From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: The unwarranted scrolling assumption Date: Thu, 17 Jun 2010 05:10:27 +0200 Message-ID: References: <87ocfcj7r4.fsf@mail.jurta.org> <87631jvpzg.fsf@gmail.com> <4C18211C.3070106@harpegolden.net> <83typ2isns.fsf@gnu.org> <83mxuuicjc.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1276744264 20350 80.91.229.12 (17 Jun 2010 03:11:04 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 17 Jun 2010 03:11:04 +0000 (UTC) Cc: david@harpegolden.net, emacs-devel@gnu.org, Stefan Monnier , storm@cua.dk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jun 17 05:11:02 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OP5VN-0007b3-TG for ged-emacs-devel@m.gmane.org; Thu, 17 Jun 2010 05:11:02 +0200 Original-Received: from localhost ([127.0.0.1]:54871 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OP5VK-0000Is-NY for ged-emacs-devel@m.gmane.org; Wed, 16 Jun 2010 23:10:58 -0400 Original-Received: from [140.186.70.92] (port=43767 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OP5VC-0000Dz-25 for emacs-devel@gnu.org; Wed, 16 Jun 2010 23:10:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OP5V9-0005lb-UG for emacs-devel@gnu.org; Wed, 16 Jun 2010 23:10:49 -0400 Original-Received: from mail-gy0-f169.google.com ([209.85.160.169]:56611) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OP5V9-0005lT-S6; Wed, 16 Jun 2010 23:10:47 -0400 Original-Received: by gyg4 with SMTP id 4so5439836gyg.0 for ; Wed, 16 Jun 2010 20:10:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=h3E1BC1sB5zGz8DtXqR96I8PN3Orjdz/eD/nu+mthXA=; b=Pht5RsOBFR0npwUpkiZjpBkdqsjh5DjA9yoOpNUmOaTedXuAHDuLJilKdRoQrzXv2H aUgsq9QRG3ELzYUTTXYa8sSRofBBN7dQSvXAt5CHc409U87OCTBsYUr5BIPed7J7ZpBx fA+6ZioBNeVPdXMNVAV+7bg6D8X/60Zj4wnm4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=B9Ns5RUsX3qpTZqfqcreBALb/lFoSE0waa3RSVEF/le3CuFRhN9zzTzVAcScX5puc/ lQ5CdnjiYwdSHx4BNzOTdFPk7AJBLvkz6nFQ9ANETmGdc9C32h4JTZFpWtLCbbvknxge R64u2kn7gWx+oniBrT5JW8mOQA2HDvhvlsYI8= Original-Received: by 10.101.5.31 with SMTP id h31mr8202353ani.158.1276744247165; Wed, 16 Jun 2010 20:10:47 -0700 (PDT) Original-Received: by 10.100.154.15 with HTTP; Wed, 16 Jun 2010 20:10:27 -0700 (PDT) In-Reply-To: <83mxuuicjc.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126054 Archived-At: On Thu, Jun 17, 2010 at 5:05 AM, Eli Zaretskii wrote: >> From: Stefan Monnier >> Cc: Lennart Borgman , =C2=A0storm@cua.dk, =C2= =A0emacs-devel@gnu.org, =C2=A0david@harpegolden.net >> Date: Wed, 16 Jun 2010 20:54:52 -0400 >> >> Indeed what he suggests is probably impossible. =C2=A0But the end result= he's >> after is definitely possible: move the window-start as little as possibl= e >> (tho still, line by line) to keep point displayed. > > xdisp.c already tries to do that, we just need to find out why it > fails in this particular case. After trying to restore the clip_changed value when save-restriction, widen etc unnecessarily changed I suddenly wonder why they changed it. Is not this something that only redisplay should handle? redisplay_can easily save the clipping when it sets clip_changed to 0 and compare with that when it enters redisplay_window and set clip_changed to 1 if the saved clipping does not match. Does that sound reasonable? (I do not know if I am missing something.)