[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unfreezing the display during auto-repeated scrolling. Simpler appro

From: Alan Mackenzie
Subject: Re: Unfreezing the display during auto-repeated scrolling. Simpler approach.
Date: Mon, 24 Nov 2014 16:00:22 +0000
User-agent: Mutt/1.5.21 (2010-09-15)

Good evening, David.

On Mon, Nov 24, 2014 at 12:53:55PM +0100, David Kastrup wrote:
> Tassilo Horn <address@hidden> writes:

> > Alan Mackenzie <address@hidden> writes:

> >> It's CC Mode's fontification, rather than the display engine, which is
> >> slow here.  But in a large window, even Emacs Lisp Mode can only just
> >> keep up: On my 2.6 GHz Athlon II, with a 66 line window, and the
> >> keyboard auto-repeating every 0.024s, fontifying and displaying a
> >> screen took ~0.018s.  There's not a lot of spare time for fancier
> >> fontification.

> > Indeed.

> >>> But still I think the variable's name is a bit misleading.  I
> >>> expected to see the text that scrolls by black on white, i.e., using
> >>> the default face similar to having `jit-lock-defer-time' set to some
> >>> non-nil value.  But instead the text that scrolls by and is visible
> >>> is fontified using the normal font-lock faces.

> >> :-).  I had quite some trouble coming up with a name for the option.
> >> Something like
> >> `assume-default-face-for-nondisplayed-screens-in-scrolling' would be
> >> more accurate, but a bit of a mouthful.  If you've any suggestions for
> >> improvement, post them!

> > Maybe something like `font-lock-omit-nondisplayed-screens-on-scoll'?

> font-lock-preempt-when-scrolling

That's brilliant!  Though I think preempt-font-lock-when-scrolling would
be better still, since the variable isn't part of the font-lock package.

> -- 
> David Kastrup

Alan Mackenzie (Nuremberg, Germany).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]