GNU bug report logs -
#41002
Undo breaks inhibit-read-only text property
Previous Next
Full log
View this message in rfc822 format
Filipp Gunbin <fgunbin <at> 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
This bug report was last modified 5 years and 33 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.