GNU bug report logs -
#53294
29.0.50; Indirect font changes incorrectly affecting original buffer
Previous Next
Reported by: Andrew Hyatt <ahyatt <at> gmail.com>
Date: Sun, 16 Jan 2022 05:14:01 UTC
Severity: normal
Found in version 29.0.50
Fixed in version 29.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
Message #17 received at 53294 <at> debbugs.gnu.org (full text, mbox):
On Sun, Jan 16, 2022 at 05:00 PM Eli Zaretskii <eliz <at> gnu.org>
wrote:
>> From: Andrew Hyatt <ahyatt <at> gmail.com> Cc: 53294 <at> debbugs.gnu.org
>> Date: Sun, 16 Jan 2022 09:43:16 -0500 Yes, the non-nil CLONE
>> argument is essential to reproduce. But that just means the
>> indirect buffer will inherit the state from the direct buffer.
>> It doesn't imply that changes made to the indirect buffer's
>> state will affect the original buffer, which is what is
>> happening here.
>
> But "inheriting" the state means the indirect buffer gets the
> copy of the variables of the original buffer, and that is not a
> deep copy, AFAIU.
>
> Stefan, any comments on this issue?
Sorry, I may have been unclear. I'm not disagreeing - what you
just said is correct. But, because of that, it's a bug for code to
make an indirect buffer, then perform operations on it via setcdr
or setf like things, which then will affect the original buffer's
variables.
Alternatively, it'd perhaps would be a better fix to make the
indirect buffer's copy a deep copy instead of the shallow copy it
is now, so that these situations don't arise. I don't have a patch
for that, though, but could create one if you thought it was a
good idea.
This bug report was last modified 3 years and 149 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.