GNU bug report logs - #31325
27.0.50; PROPOSAL: introduce a new function to recenter without redisplaying the frame

Previous Next

Package: emacs;

Reported by: John Shahid <jvshahid <at> gmail.com>

Date: Tue, 1 May 2018 00:49:02 UTC

Severity: wishlist

Found in version 27.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: John Shahid <jvshahid <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 31325 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
Subject: Re: bug#31325: 27.0.50;
 PROPOSAL: introduce a new function to recenter without redisplaying
 the frame
Date: Sun, 01 Jul 2018 17:25:18 +0000
Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Sun, 01 Jul 2018 20:03:21 +0300
>> From: Eli Zaretskii <eliz <at> gnu.org>
>> Cc: 31325 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca
>>
>> Alternatively, we could simply make 'recenter' behave specially in
>> interactive invocations.  But in any case, incompatible changes in
>> behavior are bad, and should be avoided.
>
> Or maybe invert the meaning of the new argument?

That isn't very ideal. The whole point from this change is not to force
lisp callers to change anything. If lisp callers have to change how they
call `recenter' they might as well change the call to be

   (let ((recenter-redisplay nil)) (recenter))

Few days ago I noticed the same flickering behavior in
`xref-find-definitions' because it uses `recenter' in the
`xref-after-jump-hook'.




This bug report was last modified 6 years and 322 days ago.

Previous Next


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