From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 9159@debbugs.gnu.org
Subject: bug#9159: 24.0.50; `undo' is not as good as it should be wrt property changes
Date: Tue, 02 Aug 2011 23:13:10 +0200 [thread overview]
Message-ID: <m3hb5zwm8p.fsf@stories.gnus.org> (raw)
In-Reply-To: <D57431400FFD46D5A372207627257ABD@us.oracle.com> (Drew Adams's message of "Tue, 2 Aug 2011 13:48:03 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> I already said in the OP that "while correct" (N.B.) "it would be
> better for the property `foo' to simply be removed."
I don't think this is a bug (or should be fixed), but I wonder whether
it would make sense for Fput_text_property to just delete the property
instead of adding/setting `prop nil' to the property list in general?
That is, if I say
(put-text-property (point-min) (1+ (point-min)) 'foo nil)
today, `foo nil' is added. Perhaps it should just be ignored if not
already there, and if it's already set, then it should be removed?
If we have established that there is no semantic difference between nil
properties and missing properties, then this sounds like there could be
(very minor) memory and redisplay efficiencies to be won here.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-08-02 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 2:06 bug#9159: 24.0.50; `undo' is not as good as it should be wrt property changes Drew Adams
2011-08-02 4:16 ` Stefan Monnier
2011-08-02 17:34 ` Drew Adams
2011-08-02 19:10 ` Stefan Monnier
2011-08-02 20:48 ` Drew Adams
2011-08-02 21:13 ` Lars Magne Ingebrigtsen [this message]
2011-08-02 21:48 ` Drew Adams
2011-09-11 2:36 ` Lars Magne 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3hb5zwm8p.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=9159@debbugs.gnu.org \
--cc=drew.adams@oracle.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).