From: Peter Dyballa <Peter_Dyballa@web.de>
To: R. Clayton <rclayton@monmouth.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: byte-compile-file: emacs vs the command line.
Date: Mon, 30 Dec 2013 20:27:19 +0100 [thread overview]
Message-ID: <1DE1108B-6D86-4692-B5B9-75804CB3031D@web.de> (raw)
In-Reply-To: <201312301623.rBUGNCKG027906@rockhopper.monmouth.edu>
Am 30.12.2013 um 17:23 schrieb R. Clayton:
> Running batch emacs essentially uses compile-time
> defaults, which I've already established can't find the file being required.
>
>> And if you are building GNU Emacs yourself you can configure it with
>> --enable-locallisppath=<whichever extra paths you need> so that it will find
>> all Emacs Lisp repositories ion your system.
>
> True, but compared to calling an extra elisp function, building emacs with
> special purpose defaults seems way over the top to me, and not something I want
> to do every time I have a new directory of elisp code to search for.
OK! Then just try to add all missing extra paths to directories with local Emacs Lisp additions to load-path in the system-wide init file, site-start.el. I think in batch mode this file is loaded because 'emacs --help' tells that --batch works like -q or --no-init-file.
When you launch GNU Emacs with -Q you can check the compile-time value of load-path. I think in any of these directories you can create the site-run-file. Then determine the missing paths – if you haven't done yet – and move from your personal init file the lines which extend load-path to the site-run-file!
--
Greetings
Pete
When confronted with actual numbers, a mathematician is at a loss.
– Steffen Hokland
next prev parent reply other threads:[~2013-12-30 19:27 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
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 [this message]
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=1DE1108B-6D86-4692-B5B9-75804CB3031D@web.de \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=rclayton@monmouth.edu \
/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).