[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: byte-compile-file: emacs vs the command line.
From: |
Peter Dyballa |
Subject: |
Re: byte-compile-file: emacs vs the command line. |
Date: |
Mon, 30 Dec 2013 11:34:45 +0100 |
Am 30.12.2013 um 06:19 schrieb R. Clayton:
> EMACSLOADPATH=~/lib/emacs/lisp
THis shortens your EMACSLOADPATH to exactly the one element you specify. The
environment variable EMACSLOADPATH overrides any internally used setting of
load-path coming from compilation time. So at least you should try
EMACSLOADPATH=${EMACSLOADPATH}:~/lib/emacs/lisp ...
This way you are adding another element to what you already have set.
What you did not try yet is:
EMACSLOADPATH="" emacs --batch ...
This makes the environment variable EMACSLOADPATH empty so that GNU Emacs can
use its compile time default. Maybe this internal setting is enough and you
don't need to set EMACSLOADPATH externally… (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.)
--
Greetings
Pete
To be is to do.
– I. Kant
To do is to be.
– A. Sartre
Yabba-Dabba-Doo!
– F. Flintstone
- byte-compile-file: emacs vs the command line., R. Clayton, 2013/12/28
- Re: byte-compile-file: emacs vs the command line., R. Clayton, 2013/12/29
- Re: byte-compile-file: emacs vs the command line., Eli Zaretskii, 2013/12/29
- Re: byte-compile-file: emacs vs the command line., R. Clayton, 2013/12/30
- Re: byte-compile-file: emacs vs the command line., Thierry Volpiatto, 2013/12/30
- Re: byte-compile-file: emacs vs the command line.,
Peter Dyballa <=
- Re: byte-compile-file: emacs vs the command line., R. Clayton, 2013/12/30
- Re: byte-compile-file: emacs vs the command line., Peter Dyballa, 2013/12/30
- Re: byte-compile-file: emacs vs the command line., R. Clayton, 2013/12/31