* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
@ 2013-07-15 22:41 Roland Winkler
2013-07-15 22:48 ` Glenn Morris
0 siblings, 1 reply; 12+ messages in thread
From: Roland Winkler @ 2013-07-15 22:41 UTC (permalink / raw)
To: 14876
The node "Library Search" suggests to to set EMACSLOADPATH to some
user directory such as /home/foo/.emacs.d/lisp. Yet this does not
agree with the docstring of load-path and emacs fails miserably if
one uses
export EMACSLOADPATH=/home/foo/.emacs.d/lisp
The proper meaning of EMACSLOADPATH seems to be the one given in the
docstring of load-path saying that EMACSLOADPATH overrides the
default value of load-path specified by file `epaths.h' when Emacs
was built.
The docstring of load-path also says that an element `nil' means
"try default directory". Yet what is the "default directory" in this
context? default-directory is a buffer-local variable with default nil.
I looked into this because I was looking for a way to _extend_ the
emacs load path in a Makefile generated via autoconf.
Autoconf uses the shell script elisp-comp to compile lisp files.
This script uses
echo "(setq load-path (cons nil load-path))" > script
$EMACS -batch -q -l script -f batch-byte-compile *.el || exit $?
In such a hard-coded setting I cannot (easily) extend the load-path via
the emacs option --load. But the purpose of loading the file script
is not clear to me either.
In GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.20.1)
of 2013-03-27 on regnitz
Windowing system distributor `The X.Org Foundation', version 11.0.10706000
System Description: Ubuntu 10.04.4 LTS
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 22:41 bug#14876: 24.3; load-path and environment variable EMACSLOADPATH Roland Winkler
@ 2013-07-15 22:48 ` Glenn Morris
2013-07-15 23:11 ` Roland Winkler
2013-11-14 8:39 ` Glenn Morris
0 siblings, 2 replies; 12+ messages in thread
From: Glenn Morris @ 2013-07-15 22:48 UTC (permalink / raw)
To: Roland Winkler; +Cc: 14876
"Roland Winkler" wrote:
> The node "Library Search" suggests to to set EMACSLOADPATH to some
> user directory such as /home/foo/.emacs.d/lisp.
I don't quite see that it literally says that; but the info node should
be tidied up a little bit.
> The proper meaning of EMACSLOADPATH seems to be the one given in the
> docstring of load-path saying that EMACSLOADPATH overrides the
> default value of load-path specified by file `epaths.h' when Emacs
> was built.
Yes.
> The docstring of load-path also says that an element `nil' means
> "try default directory". Yet what is the "default directory" in this
> context?
Whatever the value is where you call `load' from.
> default-directory is a buffer-local variable with default nil.
Seems like a red-herring. Normally every buffer has a non-nil value.
> I looked into this because I was looking for a way to _extend_ the
> emacs load path in a Makefile generated via autoconf.
Use "emacs -L /path/to/add".
(cf http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12100 )
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 22:48 ` Glenn Morris
@ 2013-07-15 23:11 ` Roland Winkler
2013-07-15 23:23 ` Glenn Morris
2013-11-14 8:39 ` Glenn Morris
1 sibling, 1 reply; 12+ messages in thread
From: Roland Winkler @ 2013-07-15 23:11 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14876
On Mon Jul 15 2013 Glenn Morris wrote:
> > I looked into this because I was looking for a way to _extend_ the
> > emacs load path in a Makefile generated via autoconf.
>
> Use "emacs -L /path/to/add".
...as I was trying to explain: this does not work with a Makefile
generated via autoconf.
> (cf http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12100 )
I agree with
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12100#19
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 23:11 ` Roland Winkler
@ 2013-07-15 23:23 ` Glenn Morris
2013-07-15 23:29 ` Glenn Morris
0 siblings, 1 reply; 12+ messages in thread
From: Glenn Morris @ 2013-07-15 23:23 UTC (permalink / raw)
To: Roland Winkler; +Cc: 14876
"Roland Winkler" wrote:
>> Use "emacs -L /path/to/add".
>
> ...as I was trying to explain: this does not work with a Makefile
> generated via autoconf.
Oh, I get it now, I think.
Surely autoconf must provide _some_ way for you to customize the
command-line it uses, and if it does not, that sounds like an autoconf
bug, doesn't it? Can you do
EMACS="emacs -L /path/to/add"
or is EMACS treated literally as an executable name?
> I agree with
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12100#19
So do I; but
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14513#102
Patches welcome.
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 23:23 ` Glenn Morris
@ 2013-07-15 23:29 ` Glenn Morris
2013-07-16 0:34 ` Roland Winkler
0 siblings, 1 reply; 12+ messages in thread
From: Glenn Morris @ 2013-07-15 23:29 UTC (permalink / raw)
To: Roland Winkler; +Cc: 14876
Glenn Morris wrote:
> Surely autoconf must provide _some_ way for you to customize the
> command-line it uses, and if it does not, that sounds like an autoconf
> bug, doesn't it?
BTW, I guess you mean automake not autoconf.
Also, perhaps this an automake bug which is fixed:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11806
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 23:29 ` Glenn Morris
@ 2013-07-16 0:34 ` Roland Winkler
2013-07-16 0:55 ` Roland Winkler
2013-07-16 0:55 ` Glenn Morris
0 siblings, 2 replies; 12+ messages in thread
From: Roland Winkler @ 2013-07-16 0:34 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14876
On Mon Jul 15 2013 Glenn Morris wrote:
> Also, perhaps this an automake bug which is fixed:
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11806
Thanks for the hint. Indeed, this bug report seems to be outdated.
In GNU Automake 1.13 the script elisp-comp has been removed
completely, see
https://lists.gnu.org/archive/html/automake/2012-12/msg00038.html
(and 1.14 has been released since then, too)
For lisp files, automake 1.14 generates a Makefile using an approach
that has been completely redesigned. I need to check more carefully
whether now automake allows to extend the lisp load path.
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-16 0:34 ` Roland Winkler
@ 2013-07-16 0:55 ` Roland Winkler
2013-07-16 0:55 ` Glenn Morris
1 sibling, 0 replies; 12+ messages in thread
From: Roland Winkler @ 2013-07-16 0:55 UTC (permalink / raw)
To: Glenn Morris, 14876
On Mon Jul 15 2013 Roland Winkler wrote:
> For lisp files, automake 1.14 generates a Makefile using an approach
> that has been completely redesigned. I need to check more carefully
> whether now automake allows to extend the lisp load path.
Indeed, the automake variable AM_ELCFLAGS does exactly what I need.
Hooray.
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-16 0:34 ` Roland Winkler
2013-07-16 0:55 ` Roland Winkler
@ 2013-07-16 0:55 ` Glenn Morris
2013-07-16 1:16 ` Roland Winkler
1 sibling, 1 reply; 12+ messages in thread
From: Glenn Morris @ 2013-07-16 0:55 UTC (permalink / raw)
To: Roland Winkler; +Cc: 14876
"Roland Winkler" wrote:
> In GNU Automake 1.13 the script elisp-comp has been removed
> completely, see
>
> https://lists.gnu.org/archive/html/automake/2012-12/msg00038.html
>
> (and 1.14 has been released since then, too)
>
> For lisp files, automake 1.14 generates a Makefile using an approach
> that has been completely redesigned. I need to check more carefully
> whether now automake allows to extend the lisp load path.
Great! Looks like you should just be able to set (AM_)ELCFLAGS to -L ...
in recent automake.
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-16 0:55 ` Glenn Morris
@ 2013-07-16 1:16 ` Roland Winkler
2013-07-16 1:39 ` Glenn Morris
0 siblings, 1 reply; 12+ messages in thread
From: Roland Winkler @ 2013-07-16 1:16 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14876
On Mon Jul 15 2013 Glenn Morris wrote:
> Great! Looks like you should just be able to set (AM_)ELCFLAGS to -L ...
> in recent automake.
With automake 1.14, by default, the compilation of lisp code uses
only the emacs option -batch. It does not include the option -q.
I do not know whether this is reasonable. ...When I think about it,
this might even be considered a regression compared with the old
automake shell script elisp-comp which did use the option -q.
Should I send a bug report to the automake maintainers about this?
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-16 1:16 ` Roland Winkler
@ 2013-07-16 1:39 ` Glenn Morris
2013-07-16 3:14 ` Roland Winkler
0 siblings, 1 reply; 12+ messages in thread
From: Glenn Morris @ 2013-07-16 1:39 UTC (permalink / raw)
To: Roland Winkler; +Cc: 14876
"Roland Winkler" wrote:
> With automake 1.14, by default, the compilation of lisp code uses
> only the emacs option -batch. It does not include the option -q.
> I do not know whether this is reasonable. ...When I think about it,
> this might even be considered a regression compared with the old
> automake shell script elisp-comp which did use the option -q.
> Should I send a bug report to the automake maintainers about this?
-batch implies -q.
(I always forget that as well; it's a non-obvious relationship IMO.)
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-16 1:39 ` Glenn Morris
@ 2013-07-16 3:14 ` Roland Winkler
0 siblings, 0 replies; 12+ messages in thread
From: Roland Winkler @ 2013-07-16 3:14 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14876
On Mon Jul 15 2013 Glenn Morris wrote:
> "Roland Winkler" wrote:
> > With automake 1.14, by default, the compilation of lisp code uses
> > only the emacs option -batch. It does not include the option -q.
> > I do not know whether this is reasonable. ...When I think about it,
> > this might even be considered a regression compared with the old
> > automake shell script elisp-comp which did use the option -q.
> > Should I send a bug report to the automake maintainers about this?
>
> -batch implies -q.
>
> (I always forget that as well; it's a non-obvious relationship IMO.)
Ah, thanks.
^ permalink raw reply [flat|nested] 12+ messages in thread
* bug#14876: 24.3; load-path and environment variable EMACSLOADPATH
2013-07-15 22:48 ` Glenn Morris
2013-07-15 23:11 ` Roland Winkler
@ 2013-11-14 8:39 ` Glenn Morris
1 sibling, 0 replies; 12+ messages in thread
From: Glenn Morris @ 2013-11-14 8:39 UTC (permalink / raw)
To: 14876-done
Version: 24.4
I finally got round to updating the "Library Search" section.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2013-11-14 8:39 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-07-15 22:41 bug#14876: 24.3; load-path and environment variable EMACSLOADPATH Roland Winkler
2013-07-15 22:48 ` Glenn Morris
2013-07-15 23:11 ` Roland Winkler
2013-07-15 23:23 ` Glenn Morris
2013-07-15 23:29 ` Glenn Morris
2013-07-16 0:34 ` Roland Winkler
2013-07-16 0:55 ` Roland Winkler
2013-07-16 0:55 ` Glenn Morris
2013-07-16 1:16 ` Roland Winkler
2013-07-16 1:39 ` Glenn Morris
2013-07-16 3:14 ` Roland Winkler
2013-11-14 8:39 ` Glenn Morris
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).