From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: 47425@debbugs.gnu.org
Subject: bug#47425: 26.3; `plist-get', `plist-put' should accept a TEST function
Date: Sat, 27 Mar 2021 10:16:35 +0300 [thread overview]
Message-ID: <YF7b0zfvLKyNVGYM@protected.localdomain> (raw)
In-Reply-To: <SA2PR10MB44746CB6AF01CFEDC7844E67F3619@SA2PR10MB4474.namprd10.prod.outlook.com>
* Drew Adams <drew.adams@oracle.com> [2021-03-27 01:15]:
> Please consider adding a TEST comparer arg for plist keys.
>
> In Elisp, a plist key need not be a symbol:
>
> (plist-put (list "aaa" 1 "bbb" 2 "ccc" 3) "bbb" 42)
>
> That "works" (and no error), but it doesn't do what's expected, since
> the keys should be compared with `equal' or `string=', not `eq'.
>
> And if it were not intended that that work then Elisp would raise a
> wrong-type-argument error saying that the first arg isn't a plist.
>
> And note that the Elisp manual says:
>
> A "property list" ("plist" for short) is a list of
> paired elements. Each of the pairs associates a
> property name (usually a symbol) with a property or value.
> ^^^^^^^
That is right, I always had that problem with plist, and still
do. Amount of the coping code on my side would become redundant if
that would be corrected to have a test function.
next prev parent reply other threads:[~2021-03-27 7:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 22:13 bug#47425: 26.3; `plist-get', `plist-put' should accept a TEST function Drew Adams
2021-03-26 22:16 ` Drew Adams
2021-03-27 7:16 ` Jean Louis [this message]
2021-03-28 13:12 ` Lars Ingebrigtsen
2021-03-28 16:43 ` bug#47425: [External] : " Drew Adams
2021-03-28 19:20 ` Philipp
2021-03-28 19:27 ` Lars Ingebrigtsen
2022-06-27 10:22 ` Lars Ingebrigtsen
2022-06-27 11:31 ` Mattias Engdegård
2022-06-27 11:43 ` Lars Ingebrigtsen
2022-06-27 12:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 12:27 ` Mattias Engdegård
2022-06-27 12:44 ` Lars Ingebrigtsen
2022-06-27 13:28 ` Mattias Engdegård
2022-06-27 13:35 ` Lars Ingebrigtsen
2022-06-27 15:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 15:18 ` Lars Ingebrigtsen
2022-06-27 14:39 ` Drew Adams
2022-06-27 14:39 ` Drew Adams
2022-06-27 12:41 ` Lars Ingebrigtsen
2022-06-27 14:39 ` Drew Adams
2022-06-27 14:39 ` Drew Adams
2022-06-27 15:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-27 17:07 ` Drew Adams
2022-06-27 17:19 ` Mattias Engdegård
2022-06-27 17:22 ` Lars Ingebrigtsen
2022-06-28 15:23 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-28 15:40 ` Lars Ingebrigtsen
2022-06-29 3:33 ` bug#47425: 26.3; `plist-get', `plist-put' and proposed " Richard Stallman
2022-06-29 5:11 ` Drew Adams
2022-06-30 3:10 ` Richard Stallman
2022-06-27 17:41 ` bug#47425: 26.3; `plist-get', `plist-put' should accept a " Drew Adams
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=YF7b0zfvLKyNVGYM@protected.localdomain \
--to=bugs@gnu.support \
--cc=47425@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).