From: steve-humphreys@gmx.com
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Appending to a list
Date: Mon, 14 Dec 2020 05:23:58 +0100 [thread overview]
Message-ID: <trinity-b87ab029-1117-4489-9003-ba65e768141d-1607919838615@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87czzdyqra.fsf@web.de>
> Sent: Monday, December 14, 2020 at 5:07 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Appending to a list
>
> steve-humphreys@gmx.com writes:
>
> > Consider I have the following two templates, and want a make a list
> > named "tmplt-animal", which I can then pass to org-capture-templates.
> >
> > (setq org-capture-templates tmplt-animal)
> >
> > How can I use "push" to do that?
> >
> > -------- template code --------
> > [...]
>
> Seems your list is actually not an element to add that just happens to
> be a list, but a list of elements you want to add (but the elements are
> also lists again, ehem...)
I thought I could push element by element.
> In this case you want to `append' the lists, not `push'. You may also
> define those bindings using `defvar' if you really want to set all the
> used variables at top level.
I got inspiration from some discussions here that push is more efficient
and wanted to have a go. Yes, I do use push to make the larger list.
Have not thought about defvar before. I have read that "setq" does not
introduce a variable, but I would need some explanation about that.
> Michael.
>
>
>
next prev parent reply other threads:[~2020-12-14 4:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 20:46 Appending to a list steve-humphreys
2020-12-13 21:03 ` Joost Kremers
2020-12-13 21:30 ` Óscar Fuentes
2020-12-13 21:46 ` steve-humphreys
2020-12-13 22:37 ` Joost Kremers
2020-12-13 23:08 ` Joost Kremers
2020-12-13 22:43 ` Stefan Monnier
2020-12-13 23:25 ` steve-humphreys
2020-12-13 23:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 0:19 ` steve-humphreys
2020-12-14 0:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 2:54 ` steve-humphreys
2020-12-14 2:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 3:23 ` steve-humphreys
2020-12-14 4:07 ` Michael Heerdegen
2020-12-14 4:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 4:23 ` steve-humphreys [this message]
2020-12-14 4:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 5:13 ` steve-humphreys
2020-12-14 6:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 6:25 ` steve-humphreys
2020-12-14 5:28 ` steve-humphreys
2020-12-14 6:26 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 10:25 ` steve-humphreys
2020-12-14 5:55 ` steve-humphreys
2020-12-14 6:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 17:22 ` Michael Heerdegen
2020-12-14 18:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-15 0:17 ` steve-humphreys
2020-12-15 1:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-13 21:41 ` steve-humphreys
2020-12-13 23:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=trinity-b87ab029-1117-4489-9003-ba65e768141d-1607919838615@3c-app-mailcom-bs09 \
--to=steve-humphreys@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).