GNU bug report logs - #15045
Point jumps inappropriately around time of Semantic lexing

Previous Next

Full log

Message #74 received at 15045 <at> debbugs.gnu.org (full text, mbox):

From: David Engster <deng <at> randomsample.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: gundaetiapo <at> gmail.com, 15045 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca,
 eric <at> siege-engine.com
Subject: Re: bug#15045: Point jumps inappropriately around time of Semantic
 lexing
Date: Fri, 09 Aug 2013 07:36:07 +0200

Eli Zaretskii writes:
>> From: David Engster <deng <at> randomsample.de>
>> Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>,
>> 15045 <at> debbugs.gnu.org, "Eric M. Ludlam" <eric <at> siege-engine.com>, Eli
>> Zaretskii <eliz <at> gnu.org>
>> Date: Thu, 08 Aug 2013 22:30:26 +0200
>> 
>> However, doing redisplay in timers is not nice.
>
> Why not?

Because doing redisplay is a user-visible side effect, and in general,
timers shouldn't have those. AFAICS, any function that calls things like
`accept-process-output', `input-pending-p' or `sit-for' inside a
`save-excursion' might get an unwanted scrolling effect if point is
temporarily moved to some invisible location.

In fact, I just understood another bug in speck-mode (which is similar
to flycheck). I sometimes had unwanted scrolls there, too, and I now saw
that those also happen at every full minute while typing.

>> > Doesn't deferred jit locking necessarily have to call redisplay?
>> 
>> I would think so, too.
>
> But since jit-lock-deferred-fontify only happens when Emacs is idle,
> there's no problem with that, since Emacs enters redisplay also when
> it is idle.

I thought that the jit-lock timer is a non-idle timer, but you are
right.

-David

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.