GNU bug report logs - #78221
31.0.50; Improving *-change-functions notifications

Previous Next

Full log

Message #68 received at 78221 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 78221 <at> debbugs.gnu.org, Alan Mackenzie <acm <at> muc.de>
Subject: Re: bug#78221: 31.0.50; Improving *-change-functions notifications
Date: Sun, 04 May 2025 17:23:59 +0000

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

> I wonder if someone actually knows of a `*-change-function` which wants
> to be triggered when text-properties are modified.  I'm not 100% sure
> that I've never seen such a thing, but at least I can't remember seeing
> (nor writing) such a thing.

Me neither.
Asking LLMs will just make them hallucinate :)

> Are these property-modifications spread all over the place or can you
> point us to a few important places where they happen?

- org-edit-latex-fragment
- org-display-custom-time
- org-agenda (in special org-agenda buffers). not relevant to
  *-change-functions Org mode uses though

> I'm curious to know as well how those deal with other related "usually
> undesired" effects, such as modifying the `buffer-modified-p` flag,
> stashing the property modifications into the `buffer-undo-list`, or
> signaling errors when the buffer is read-only.

Not very well usually, until someone files a bug report.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.