From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: byte-compile-file: emacs vs the command line.
Date: Sun, 29 Dec 2013 18:26:50 +0200 [thread overview]
Message-ID: <8338lb39o5.fsf@gnu.org> (raw)
In-Reply-To: <87zjnjzlz8.fsf@UlanBator.myhome.westell.com>
> From: rclayton@monmouth.edu (R. Clayton)
> Date: Sun, 29 Dec 2013 10:59:55 -0500
>
> Why is the command-line compile failing, and how can I fix it?
>
> require uses load, and running in batch doesn't load init files. This means
> load-path doesn't contain everything it should to load local files. The fix
> is to fix load-path:
>
> $ cat rm.el
> (require 'general-utils)
>
> $ emacs --batch --exec '(byte-compile-file "rm.el")'
Like this:
$ EMACSLOADPATH=/what:/ever:/you:/need emacs -batch -f batch-byte-compile rm.el
next prev parent reply other threads:[~2013-12-29 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 22:41 byte-compile-file: emacs vs the command line R. Clayton
2013-12-29 15:59 ` R. Clayton
2013-12-29 16:26 ` Eli Zaretskii [this message]
2013-12-30 5:19 ` R. Clayton
2013-12-30 7:20 ` Thierry Volpiatto
2013-12-30 10:34 ` Peter Dyballa
2013-12-30 16:23 ` R. Clayton
2013-12-30 19:27 ` Peter Dyballa
2014-01-01 2:52 ` R. Clayton
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=8338lb39o5.fsf@gnu.org \
--to=eliz@gnu.org \
--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).