From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: append, push, and add-to-list.
Date: Mon, 05 Jul 2021 07:50:41 +0200 [thread overview]
Message-ID: <874kd9ia1a.fsf@zoho.eu> (raw)
In-Reply-To: CAGP6POKCvmP8Jvz699mRaEbUhb4CdgMDSfeNTHO_bgjP7xgBcA@mail.gmail.com
Hongyi Zhao wrote:
>> (setq lst '(a b))
>> (setq lst `(,@lst logic) ; (a b logic)
>
> You have a typo here, should be the following:
>
> ((setq lst `(,@lst logic))
Heh, yes but now there is another typo :)
It should look like this:
(setq lst '(a b))
(setq lst `(,@lst logic)) ; (a b logic)
> Wonderful examples, but how to eval multiple line lisp codes
> in scratch buffer? I only know with twice hitting of `C-j'
> for this job, as shown below:
You can use `eval-buffer' or enclose it in a `progn' perhaps.
Or, for this particular example, `let'/`let*'...
I have M-9 do `eval-last-sexp', more ergonomic IMO than
whatever is the default binding...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2021-07-05 5:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 3:18 append, push, and add-to-list Hongyi Zhao
2021-07-04 4:35 ` Jean Louis
2021-07-04 5:11 ` Hongyi Zhao
2021-07-04 11:28 ` Jean Louis
2021-07-04 13:50 ` Hongyi Zhao
2021-07-04 15:58 ` Jean Louis
2021-07-05 2:04 ` Hongyi Zhao
2021-07-04 16:01 ` [External] : " Drew Adams
2021-07-04 16:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-04 16:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 2:16 ` Hongyi Zhao
2021-07-05 3:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 4:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 5:07 ` Hongyi Zhao
2021-07-05 5:50 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2021-07-05 6:19 ` Hongyi Zhao
2021-07-05 5:06 ` Jean Louis
2021-07-05 6:22 ` Hongyi Zhao
2021-07-05 6:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2021-07-05 14:37 Drew Adams
2021-07-05 14:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 15:19 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-05 16:46 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 19:54 ` Jean Louis
2021-07-06 20:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 15:41 ` tomas
2021-07-05 16:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 17:21 ` tomas
2021-07-06 1:17 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 18:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 18:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 18:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 18:39 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-05 20:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 19:57 ` Jean Louis
2021-07-06 20:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 19:56 ` Jean Louis
2021-07-06 20:15 ` 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=874kd9ia1a.fsf@zoho.eu \
--to=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).