GNU bug report logs - #12170
save-excursion fails boundary case with recenter

Previous Next

Full log

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

From: npostavs <at> users.sourceforge.net
To: control <at> debbugs.gnu.org
Subject: Re: bug#12170: save-excursion fails boundary case with recenter
Date: Fri, 24 Mar 2017 23:50:15 -0400

tags 12170 notabug
close 12170
quit

"Bill Brodie" <wbrodie <at> panix.com> writes:

> From my point of view (the OP), I've generally used save-excursion to
> assemble or manipulate information elsewhere in the buffer or in other
> buffers, without explicit reference to window displays.  This seems like a
> natural restriction.
>
> I've modified my original code to perform the window operations outside the
> form.  Thanks for the illuminating discussion.
>
> -----Original Message-----
> From: Eli Zaretskii [mailto:eliz <at> gnu.org] 
>
> IMO, save-excursion is simply not designed to make sure display isn't
> changed in such cases.  It's for excursions into other portions of the
> buffer for processing those other parts, without affecting display.
> If the processing also scrolls the screen or calls recenter or
> otherwise affects the display, all bets are off, because scrolling can
> legitimately move point, and when that happens, it is no longer clear
> that restoring point should take precedence over window-start etc.

Previous Next

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