From: Eli Zaretskii <eliz@gnu.org>
To: Filipp Gunbin <fgunbin@fastmail.fm>
Cc: 41002@debbugs.gnu.org, egnartsms@gmail.com, larsi@gnus.org
Subject: bug#41002: Undo breaks inhibit-read-only text property
Date: Sat, 09 May 2020 16:49:28 +0300 [thread overview]
Message-ID: <838si1fcbb.fsf@gnu.org> (raw)
In-Reply-To: <m2o8qxp6z0.fsf@fastmail.fm> (message from Filipp Gunbin on Sat, 09 May 2020 16:34:43 +0300)
> From: Filipp Gunbin <fgunbin@fastmail.fm>
> Cc: egnartsms@gmail.com, 41002@debbugs.gnu.org, larsi@gnus.org
> Date: Sat, 09 May 2020 16:34:43 +0300
>
> > I think you are right: we need to augment this with something that
> > pays attention to the inhibit-read-only property. Would you like to
> > suggest a patch?
>
> That property is checked in INTERVAL_WRITABLE_P just above, it looks
> fine.
That tests if the interval is _not_ writable. But the problem is not
triggered by the interval, it is triggered by characters after the
interval, is it not?
> The problem is I don't know what the "if" I cited is for.
Hopefully, Lars will answer that.
> > Btw, how is this related to undo?
>
> Before undo, we seem to have one interval spanning all the text. After
> undo, there appears a short interval on which "i->position + LENGTH (i)
> < end" triggers.
Right, thanks. So this situation could be recreated without any undo
in the recipe, right?
next prev parent reply other threads:[~2020-05-09 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 10:38 bug#41002: Undo breaks inhibit-read-only text property Serhii Mozghovyi
2020-05-02 17:33 ` Filipp Gunbin
2020-05-02 19:09 ` Serhii Mozghovyi
2020-05-03 3:22 ` Filipp Gunbin
2020-05-09 7:37 ` Eli Zaretskii
2020-05-09 13:34 ` Filipp Gunbin
2020-05-09 13:49 ` Eli Zaretskii [this message]
2020-05-09 16:55 ` Filipp Gunbin
2020-05-19 12:12 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838si1fcbb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=41002@debbugs.gnu.org \
--cc=egnartsms@gmail.com \
--cc=fgunbin@fastmail.fm \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.