[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#41002: Undo breaks inhibit-read-only text property
From: |
Lars Ingebrigtsen |
Subject: |
bug#41002: Undo breaks inhibit-read-only text property |
Date: |
Tue, 19 May 2020 14:12:13 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Filipp Gunbin <fgunbin@fastmail.fm> writes:
> @@ -2301,0 +2301,4 @@
> + if (i->position + LENGTH (i) < end
> + && (!NILP (BVAR (current_buffer, read_only))
> + && NILP (Vinhibit_read_only)))
> + xsignal1 (Qbuffer_read_only, Fcurrent_buffer ());
>
> So if there happens to be an (writeable) interval ending before "end"
> (the end of the region we're killing with C-w), we will signal that the
> buffer is read-only. This may be read as "if we're going over the
> boundary of an interval, then check the _buffer_ read-onliness". Maybe
> Lars, as the author of this code, could comment on this.
Hm... I've re-read the original patch, and I don't really have any
recollection of what my original thought here was, I'm afraid.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#41002: Undo breaks inhibit-read-only text property, Serhii Mozghovyi, 2020/05/01
- bug#41002: Undo breaks inhibit-read-only text property, Filipp Gunbin, 2020/05/02
- bug#41002: Undo breaks inhibit-read-only text property, Serhii Mozghovyi, 2020/05/02
- bug#41002: Undo breaks inhibit-read-only text property, Filipp Gunbin, 2020/05/02
- bug#41002: Undo breaks inhibit-read-only text property, Eli Zaretskii, 2020/05/09
- bug#41002: Undo breaks inhibit-read-only text property, Filipp Gunbin, 2020/05/09
- bug#41002: Undo breaks inhibit-read-only text property, Eli Zaretskii, 2020/05/09
- bug#41002: Undo breaks inhibit-read-only text property, Filipp Gunbin, 2020/05/09
- bug#41002: Undo breaks inhibit-read-only text property,
Lars Ingebrigtsen <=