From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 36190@debbugs.gnu.org
Subject: bug#36190: 27.0.50; `put-text-property' etc. with buffer argument calls current buffer's `after-change-functions'
Date: Sat, 06 Jul 2019 11:08:41 +0300 [thread overview]
Message-ID: <8336jja8l2.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBc85g11BWqVFViAURuh3sqrphWbUNJ6KvuKcF_F8u4L0Q@mail.gmail.com> (message from Pip Cet on Sat, 15 Jun 2019 19:27:30 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Sat, 15 Jun 2019 19:27:30 +0000
> Cc: 36190@debbugs.gnu.org
>
> > Looks better to me, but I'd suggest a comment explaining why we do
> > such an unusual thing.
>
> Sounds good to me. The attached patch contains the comments and a hint
> in the documentation. (Maybe the comments should be a FIXME, because
> there's really no need to switch buffers at all when there are no
> applicable hooks?)
I'm okay with adding such a FIXME.
> Obviously, feel free to reword as you consider appropriate.
LGTM, with a couple of minor comments below. Feel free to push after
fixing those.
> + /* Ensure we run the modification hooks for the right buffer,
> + without switching buffers twice (bug 36190). */
^^
Here and elsewhere please keep 2 spaces between the period and "*/"
> + if (BUFFERP (object) && XBUFFER (object) != current_buffer)
> + {
> + ptrdiff_t count = SPECPDL_INDEX ();
> + record_unwind_current_buffer ();
> + set_buffer_internal (XBUFFER (object));
> + return unbind_to (count, Fremove_list_of_text_properties (start, end,
> + list_of_properties,
> + object));
> + }
The indentation here is too deep; suggest reformatting, e.g., by
inserting a newline before Fremove_list_of_text_properties, and then
reindenting the rest.
next prev parent reply other threads:[~2019-07-06 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 13:48 bug#36190: 27.0.50; `put-text-property' etc. with buffer argument calls current buffer's `after-change-functions' Pip Cet
2019-06-13 16:36 ` Eli Zaretskii
2019-06-13 18:48 ` Pip Cet
2019-06-13 19:05 ` Eli Zaretskii
2019-06-13 19:27 ` Eli Zaretskii
2019-06-13 19:42 ` Pip Cet
2019-06-13 20:01 ` Eli Zaretskii
2019-06-13 20:57 ` Pip Cet
2019-06-13 21:37 ` Pip Cet
2019-06-14 7:41 ` Eli Zaretskii
2019-06-14 11:14 ` Pip Cet
2019-06-14 12:10 ` Eli Zaretskii
2019-06-15 15:14 ` Pip Cet
2019-06-15 15:23 ` Eli Zaretskii
2019-06-15 19:27 ` Pip Cet
2019-07-06 8:08 ` Eli Zaretskii [this message]
2019-07-06 15:27 ` Pip Cet
2019-07-06 16:22 ` Eli Zaretskii
2019-06-14 7:36 ` Eli Zaretskii
2019-06-17 11:38 ` Pip Cet
2019-06-17 15:59 ` Eli Zaretskii
2019-06-18 17:14 ` Pip Cet
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=8336jja8l2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36190@debbugs.gnu.org \
--cc=pipcet@gmail.com \
/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.