GNU bug report logs - #75170
add-to-alist: new function

Previous Next

Full log

View this message in rfc822 format

From: Roland Winkler <winkler <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 75170 <at> debbugs.gnu.org, rpluim <at> gmail.com, acorallo <at> gnu.org, Stefan Kangas <stefankangas <at> gmail.com>, monnier <at> gnu.org
Subject: bug#75170: add-to-alist: new function
Date: Tue, 21 Jan 2025 13:21:01 -0600

On Tue, Jan 21 2025, Eli Zaretskii wrote:
> Can someone tell me again why add-to-list doesn't fit the bill of
> being a tool easy for end-users?  I've been using it in my init files
> to customize stuff like default-frame-alist since about forever.

The following was my answer from end of last year:

On Sun, Dec 29 2024, Roland Winkler wrote:
> The advantage I see for also having the function add-to-alist is the
> following:
>
> add-to-list checks for the presence of an element in a list.  In the
> case of alists, this means it checks for the presence of associations.
> You cannot easily modify an existing association with add-to-list.  If
> you have an alist with association (foo . bar) and you call add-to-list
> with an element (foo . baz), add-to-list will not remove the association
> (foo . bar), but the alist will then contain both associations.
>
> add-to-alist checks for the presence of keys and it makes sure that each
> key appears only once in an alist.  By default, it replaces the value of
> an existing key.  This makes it easy to modify an existing association.
> Only with the optional arg NO-REPLACE non-nil, it will preserve an
> existing association.

Previous Next

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