From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry OReilly Newsgroups: gmane.emacs.bugs Subject: bug#14508: scroll-conservatively==1 not honored for fast line by line navigation up Date: Fri, 7 Jun 2013 12:37:08 -0400 Message-ID: References: <83bo7q0ydw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e0149d290c10f2204de930ad9 X-Trace: ger.gmane.org 1370623090 24980 80.91.229.3 (7 Jun 2013 16:38:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 7 Jun 2013 16:38:10 +0000 (UTC) Cc: 14508@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jun 07 18:38:09 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ukzg1-000513-1T for geb-bug-gnu-emacs@m.gmane.org; Fri, 07 Jun 2013 18:38:09 +0200 Original-Received: from localhost ([::1]:53979 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ukzg0-0002Kc-La for geb-bug-gnu-emacs@m.gmane.org; Fri, 07 Jun 2013 12:38:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54122) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ukzfv-0002KX-Od for bug-gnu-emacs@gnu.org; Fri, 07 Jun 2013 12:38:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ukzfu-0008Jn-2a for bug-gnu-emacs@gnu.org; Fri, 07 Jun 2013 12:38:03 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:40102) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ukzft-0008Jj-V6 for bug-gnu-emacs@gnu.org; Fri, 07 Jun 2013 12:38:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.72) (envelope-from ) id 1Ukzfu-00086b-QN for bug-gnu-emacs@gnu.org; Fri, 07 Jun 2013 12:38:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Barry OReilly Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 07 Jun 2013 16:38:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14508 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 14508-submit@debbugs.gnu.org id=B14508.137062304031029 (code B ref 14508); Fri, 07 Jun 2013 16:38:02 +0000 Original-Received: (at 14508) by debbugs.gnu.org; 7 Jun 2013 16:37:20 +0000 Original-Received: from localhost ([127.0.0.1]:56693 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UkzfD-00084J-0N for submit@debbugs.gnu.org; Fri, 07 Jun 2013 12:37:19 -0400 Original-Received: from mail-ob0-f171.google.com ([209.85.214.171]:64922) by debbugs.gnu.org with esmtp (Exim 4.72) (envelope-from ) id 1UkzfA-00083k-4o for 14508@debbugs.gnu.org; Fri, 07 Jun 2013 12:37:16 -0400 Original-Received: by mail-ob0-f171.google.com with SMTP id dn14so6877634obc.2 for <14508@debbugs.gnu.org>; Fri, 07 Jun 2013 09:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=rFGWQMOgvkCdOiU4b3VvzuFpxWg4uORCI3GLxXgL9NU=; b=1EU4SUcojI6fAXJzpHCI+lqAKb9dUZBu81IWS2lldGCxxtgZ+O4YH3whBS4udjJJpS dl4EWBNWZocd1h2gwBoBUV8vchgcvQW93alzgDogBTJiNeT4oz9yJPgMoopYd9X0FK1L JUfq7pcwk1g7ZYPx2+luHH9o2Nh5tsZLVglDdP6sTOLHbz5DqvzZeXSnsKeBEwhbD0wa PLpvMt6DsQiGpi2XFYJX6pKX5pThwgGyENyBUmWHb920tr+8klTc2a0qflQbin9OqQ1h V+M2B4Y+PECjNGhlzgthorA3Y8Eq6Blzw2oniC4yflihKCNCYpJbt4cn6L57zBzBpjqI gOuw== X-Received: by 10.182.108.230 with SMTP id hn6mr22013201obb.25.1370623028823; Fri, 07 Jun 2013 09:37:08 -0700 (PDT) Original-Received: by 10.76.69.234 with HTTP; Fri, 7 Jun 2013 09:37:08 -0700 (PDT) In-Reply-To: <83bo7q0ydw.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.13 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:74873 Archived-At: --089e0149d290c10f2204de930ad9 Content-Type: text/plain; charset=ISO-8859-1 > You see this on scroll ups, because they are slightly slower than > scroll downs, and the difference is enough to trigger this with > higher probability when you go up. Closely related, I define these commands (byte compiled): (defvar my-leap-scroll-size 16) (define-key evil-normal-state-map ";" nil) (define-key evil-motion-state-map ";" (lambda () (interactive) (scroll-up my-leap-scroll-size) (evil-next-line my-leap-scroll-size))) (define-key evil-normal-state-map "'" nil) (define-key evil-motion-state-map "'" (lambda () (interactive) (scroll-down my-leap-scroll-size) (evil-previous-line my-leap-scroll-size))) In the same C++ buffer as before, when I hold to repeat the above command that scrolls up*, the display doesn't update at all until I release the key to stop the repeat. As you indicated it may, the scroll down can keep up in this case. I turned font locking off and the scroll up redisplay keeps up. I also tried this in a Python buffer with font lock on and these commands keep up much better. Is it that the C/C++ font locking is more complex? Has C/C++ major mode been performance tuned for this use case? Maybe I can experiment with my local configuration to temporarily disable font locking while I'm scrolling up fast -- seeing non font locked code fly by would be better than nothing at all. * Assume I use "up" and "down" in the majority usage, opposite of Emacs terminology --089e0149d290c10f2204de930ad9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > You see this on scroll ups, because they are slightly slower than
&= gt; scroll downs, and the difference is enough to trigger this with
>= higher probability when you go up.

Closely related, I define these = commands (byte compiled):

=A0 (defvar my-leap-scroll-size 16)
=A0 (define-key evil-normal-stat= e-map ";" nil)
=A0 (define-key evil-motion-state-map ";&q= uot;
=A0=A0=A0 (lambda ()
=A0=A0=A0=A0=A0 (interactive)
=A0=A0=A0= =A0=A0 (scroll-up my-leap-scroll-size)
=A0=A0=A0=A0=A0 (evil-next-line my-leap-scroll-size)))
=A0 (define-key e= vil-normal-state-map "'" nil)
=A0 (define-key evil-motion-= state-map "'"
=A0=A0=A0 (lambda ()
=A0=A0=A0=A0=A0 (in= teractive)
=A0=A0=A0=A0=A0 (scroll-down my-leap-scroll-size)
=A0=A0=A0=A0=A0 (evil-previous-line my-leap-scroll-size)))

In the sa= me C++ buffer as before, when I hold to repeat the above
command that sc= rolls up*, the display doesn't update at all until I
release the key= to stop the repeat. As you indicated it may, the
scroll down can keep up in this case. I turned font locking off and
the = scroll up redisplay keeps up. I also tried this in a Python buffer
with = font lock on and these commands keep up much better. Is it that
the C/C+= + font locking is more complex? Has C/C++ major mode been
performance tuned for this use case? Maybe I can experiment with my
loca= l configuration to temporarily disable font locking while I'm
scroll= ing up fast -- seeing non font locked code fly by would be
better than n= othing at all.

* Assume I use "up" and "down" in the majority usag= e, opposite of
=A0 Emacs terminology

--089e0149d290c10f2204de930ad9--