From: "Roland Winkler" <winkler@gnu.org>
To: emacs-devel@gnu.org
Cc: Ulrich Mueller <ulm@gentoo.org>, Christian Egli <christian.egli@sbs.ch>
Subject: emacs options -batch and --no-site-file
Date: Wed, 4 Jun 2014 21:13:43 -0500 [thread overview]
Message-ID: <53847.35041.828701.21391@gargle.gargle.HOWL> (raw)
Following BBDB bug report http://savannah.nongnu.org/bugs/?42482
we have had a discussion about how to call emacs in the Makefile
byte-compiling the lisp sources of BBDB. The option -batch implies
--no-init-file, but it does not imply --no-site-file. Is there a
reason for the latter? Is there a "recommended strategy" which of
these options such a Makefile should / should not use?
Thanks,
Roland
next reply other threads:[~2014-06-05 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 2:13 Roland Winkler [this message]
2014-06-05 7:24 ` emacs options -batch and --no-site-file Glenn Morris
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=53847.35041.828701.21391@gargle.gargle.HOWL \
--to=winkler@gnu.org \
--cc=christian.egli@sbs.ch \
--cc=emacs-devel@gnu.org \
--cc=ulm@gentoo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).