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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Daniel Colascione <dancol <at> dancol.org>
Cc: 78221 <at> debbugs.gnu.org, yantar92 <at> posteo.net, monnier <at> iro.umontreal.ca
Subject: bug#78221: `inhibit-recording-text-property-changes`
Date: Tue, 13 May 2025 15:09:10 +0300

> Date: Mon, 12 May 2025 21:12:29 -0700
> From: Daniel Colascione <dancol <at> dancol.org>
> CC: 78221 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
>  Ihor Radchenko <yantar92 <at> posteo.net>,
>  João Távora <joaotavora <at> gmail.com>
> 
> >The only case I have found so far where we do want to record
> >text-property changes (not to run *-change-functions, but to mark the
> >buffer as modified and to record the changes in the undo-list) is the
> >`enriched-mode`.
> 
> Can we just delete enriched mode? Good idea, but the world ended up going in a different direction.

This is a tangent, but I don't see any sense in deleting
enriched-mode.  It's a stand-alone mode, which doesn't impose any
requirements on the rest of Emacs, and consumes almost no maintenance
(grand total of 10 real changes in the last 10 years).

OTOH, it provides a ready-to-use infrastructure for any feature that
wants to make text properties persistent.  We needed that for
etc/HELLO (to avoid the need to encode it in ISO 2022 so as to
preserve the charset information), and it was very easy to leverage it
for that purpose.  If enriched-mode didn't exist back then, we'd have
a much harder problem to solve.

Previous Next

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