From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: 'emacs -batch -eval ... -f ...' outputs everyday crunching to stderr?
Date: Thu, 04 Sep 2014 20:52:27 +0200 [thread overview]
Message-ID: <87oauvnrpw.fsf@debian.uxu> (raw)
In-Reply-To: mailman.8241.1409820712.1147.help-gnu-emacs@gnu.org
Aurélien Aptel <aurelien.aptel@gmail.com> writes:
> You can use `append' instead of `cl-concatenate'.
> It's a builtin.
You mean like this?
(setq l1 '(1 2 3))
(setq l2 '(four five six))
(setq l1 (append l1 l2))
Yeah, that's better. Then I don't need to bring in CL
for the Makefile so when I compile individual files
those will complain if they use CL and I don't bring it
in for that particular file. Thank you!
And idea as to the output to stderr?
--
underground experts united
next prev parent reply other threads:[~2014-09-04 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 2:31 'emacs -batch -eval ... -f ...' outputs everyday crunching to stderr? Emanuel Berg
[not found] ` <mailman.8241.1409820712.1147.help-gnu-emacs@gnu.org>
2014-09-04 18:52 ` Emanuel Berg [this message]
2014-09-20 23:15 ` Emanuel Berg
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=87oauvnrpw.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@gnu.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.
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).