From: Diego Nicola Barbato <dnbarbato@posteo.de>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 38399@debbugs.gnu.org
Subject: bug#38399: Recent $EMACSLOADPATH changes break emacs-org
Date: Thu, 28 Nov 2019 15:25:07 +0100 [thread overview]
Message-ID: <87mucg84e4.fsf@GlaDOS.home> (raw)
In-Reply-To: <87a78gtwk4.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 28 Nov 2019 14:11:07 +0900")
Hello Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
>> It stands to reason that the elisp libraries provided by Emacs itself
>> shouldn’t be in EMACSLOADPATH in the first place as they are already in
>> ‘load-path’ to which the directories in EMACSLOADPATH are prepended (as
>> described in the Emacs manual).
>
> That's not true; when using EMACSLOADPATH the Emacs' bundled libraries
> must be included explicitly, or an empty item be present (which means,
> an extra ':' present).
>
> See (elisp)Library Search:
>
> An empty element in the value of the environment variable,
> whether trailing (as in the above example), leading, or embedded, is
> replaced by the default value of ‘load-path’ as determined by the
> standard initialization procedure. If there are no such empty
> elements, then ‘EMACSLOADPATH’ specifies the entire ‘load-path’.
> You must include either an empty element, or the explicit path to
> the directory containing the standard Lisp files, else Emacs will
> not function.
Thanks for the clarification! And sorry for the noise, I should have
read it more closely.
Regards,
Diego
next prev parent reply other threads:[~2019-11-28 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 10:00 bug#38399: Recent $EMACSLOADPATH changes break emacs-org Diego Nicola Barbato
2019-11-28 5:11 ` Maxim Cournoyer
2019-11-28 14:25 ` Diego Nicola Barbato [this message]
2019-12-07 4:32 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mucg84e4.fsf@GlaDOS.home \
--to=dnbarbato@posteo.de \
--cc=38399@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.