From: Jean-Christophe Helary <brandelune@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: interference between package and exec-path values ?
Date: Sat, 20 Oct 2018 18:14:38 +0900 [thread overview]
Message-ID: <C75E0B80-1541-4C97-86C7-4B5FEE101961@gmail.com> (raw)
In-Reply-To: <83mur9unua.fsf@gnu.org>
> On Oct 20, 2018, at 15:35, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Jean-Christophe Helary <brandelune@gmail.com>
>> Date: Sat, 20 Oct 2018 10:55:23 +0900
>>
>>> Of course! You are using 'append' incorrectly. Evaluate
>>>
>>> (append "/usr/local/bin/" exec-path)
>>>
>>> and you will see what kind of result this produces.
>>
>> Yes but :)
>>
>> I had this expression in my .emacs.el file for a while now and it never interfered with package.
>
> I'm sorry, I don't believe you ;-) Either that expression was not
> evaluated at all, or some other factor(s) were at work that bypassed
> the error.
:) You're wrong not to believe me and you're right that some other factors at work bypassed the error. I seem to remember that I (badly) copied that expression from some article because when Emacs does not start from the command line it does not inherit the environment variables defined by the shell and thus you have to add the /usr/local/bin path manually from within emacs parameters.
And it happens that I used to launch GUI emacs from the command line until very recently when I started to call the Emacs.app binary directly and that's when the problem started to occur.
>> Also, when I start with -q and evaluated the expressions one by one, evaluating that erroneous expression did *not* trigger the error, it's only when I started emacs without -q that the error was triggered.
>
> What do you mean by "does not trigger the error"? The evaluation
> itself will never trigger any errors, as it is valid Lisp. It's only
> when you start using the resulting value of exec-path that the
> problems pop up. Perhaps previously, the resulting exec-path was
> never used in your sessions.
Would that be possible that when starting emacs from the command line the path defined by the shell overrides that expression (not sure I'm making sense here) ?
> But it's a mistake nonetheless.
I understand that part :)
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2018-10-20 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 16:41 interference between package and exec-path values ? Jean-Christophe Helary
2018-10-19 17:24 ` Yuri Khan
2018-10-19 17:36 ` Jean-Christophe Helary
2018-10-19 17:32 ` Eli Zaretskii
2018-10-20 1:55 ` Jean-Christophe Helary
2018-10-20 6:35 ` Eli Zaretskii
2018-10-20 9:14 ` Jean-Christophe Helary [this message]
2018-10-20 10:22 ` Eli Zaretskii
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=C75E0B80-1541-4C97-86C7-4B5FEE101961@gmail.com \
--to=brandelune@gmail.com \
--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).