From: Heime <heimeborgia@protonmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emanuel Berg <incal@dataswamp.org>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Easy to add with push but not to the end of a list
Date: Mon, 28 Nov 2022 22:18:18 +0000 [thread overview]
Message-ID: <8_NTlRuvl09d4xR8LNJtkEjDfIRIXe2slBhexR8Mfr1YpTD0jqcLcgaUfrQith_p8ixmZHAq-Tigf-ca3QrktLHjdJwqPm2nUO0xQEmihwk=@protonmail.com> (raw)
In-Reply-To: <SJ0PR10MB548848DDEEAAD40E2373B9C9F3139@SJ0PR10MB5488.namprd10.prod.outlook.com>
------- Original Message -------
On Monday, November 28th, 2022 at 9:56 PM, Drew Adams <drew.adams@oracle.com> wrote:
> > I agree there should be such a function in vanilla Emacs.
> > Maybe something like this?
> >
> > (defun push-last (elem lst)
> > (when (listp lst)
> > (setcdr (last lst) (list elem))
> > lst))
>
>
> As I said, there are umpteen different meanings /
> behaviors for "add an element to the end of a list".
>
> (setcdr (last lst) (list elem)) is one such behavior.
>
> And that's just as succinct as (push-last elem lst),
> and clearer. It makes crystal clear that you're
> opting for list modification.
There are never any qualms about putting something at the beginning
of a list. One should not take a different attitude to adding after
the last entry.
next prev parent reply other threads:[~2022-11-28 22:18 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 2:26 Easy to add with push but not to the end of a list Heime
2022-11-28 2:43 ` [External] : " Drew Adams
2022-11-28 3:45 ` Heime
2022-11-28 6:11 ` Drew Adams
2022-11-28 20:00 ` Emanuel Berg
2022-11-28 5:18 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-28 20:19 ` Emanuel Berg
2022-11-28 21:56 ` [External] : " Drew Adams
2022-11-28 22:45 ` Emanuel Berg
2022-11-28 22:01 ` Heime
2022-11-28 22:24 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-11-28 22:58 ` Emanuel Berg
2022-11-30 14:10 ` tomas
2022-11-30 16:12 ` Emanuel Berg
2022-11-28 22:46 ` Emanuel Berg
2022-11-28 22:50 ` Emanuel Berg
2022-11-29 5:23 ` tomas
2022-11-29 5:32 ` Emanuel Berg
2022-11-29 7:56 ` Heime
2022-11-29 8:33 ` Marcin Borkowski
2022-11-29 10:00 ` Emanuel Berg
2022-11-29 10:05 ` Emanuel Berg
2022-11-29 10:15 ` Heime
2022-11-29 8:38 ` tomas
2022-11-29 9:54 ` Emanuel Berg
2022-11-29 8:17 ` Marcin Borkowski
2022-11-29 8:44 ` tomas
2022-11-29 12:08 ` Dr Rainer Woitok
2022-11-29 19:54 ` Of cars and mice [was: Easy to add with push but not to the end of a list] tomas
2022-11-30 1:17 ` Emanuel Berg
2022-11-30 1:13 ` Easy to add with push but not to the end of a list Emanuel Berg
2022-11-28 19:59 ` Emanuel Berg
2022-11-28 21:56 ` [External] : " Drew Adams
2022-11-28 22:18 ` Heime [this message]
2022-11-28 22:41 ` Drew Adams
2022-11-29 11:17 ` Dr Rainer Woitok
2022-11-30 17:10 ` Michael Heerdegen
2022-11-30 18:17 ` [External] : " Drew Adams
2022-11-30 19:30 ` Emanuel Berg
2022-12-01 15:11 ` Michael Heerdegen
2022-12-01 17:25 ` Emanuel Berg
2022-12-03 21:29 ` Michael Heerdegen
2022-12-05 23:35 ` Emanuel Berg
2022-12-06 1:36 ` Michael Heerdegen
2022-12-06 1:43 ` Emanuel Berg
2022-12-06 2:17 ` Michael Heerdegen
2022-12-06 2:40 ` Emanuel Berg
2022-12-06 13:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-12-06 14:45 ` Michael Heerdegen
2022-12-06 2:52 ` Emanuel Berg
2022-12-06 17:22 ` Michael Heerdegen
2022-12-06 22:30 ` Emanuel Berg
2022-12-08 23:15 ` Michael Heerdegen
2022-12-28 23:52 ` Emanuel Berg
2022-12-31 16:57 ` Michael Heerdegen
2022-12-31 22:09 ` Emanuel Berg
2023-01-01 12:16 ` Michael Heerdegen
2023-01-08 4:40 ` Emanuel Berg
2023-01-09 6:32 ` Emanuel Berg
2023-01-14 12:05 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8_NTlRuvl09d4xR8LNJtkEjDfIRIXe2slBhexR8Mfr1YpTD0jqcLcgaUfrQith_p8ixmZHAq-Tigf-ca3QrktLHjdJwqPm2nUO0xQEmihwk=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.