From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: interference between package and exec-path values ?
Date: Sat, 20 Oct 2018 13:22:36 +0300 [thread overview]
Message-ID: <835zxwvrwz.fsf@gnu.org> (raw)
In-Reply-To: <C75E0B80-1541-4C97-86C7-4B5FEE101961@gmail.com> (message from Jean-Christophe Helary on Sat, 20 Oct 2018 18:14:38 +0900)
> From: Jean-Christophe Helary <brandelune@gmail.com>
> Date: Sat, 20 Oct 2018 18:14:38 +0900
>
> 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) ?
I don't think so. But it is quite possible that exec-path was not
used in your previous invocations.
prev parent reply other threads:[~2018-10-20 10:22 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
2018-10-20 10:22 ` Eli Zaretskii [this message]
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=835zxwvrwz.fsf@gnu.org \
--to=eliz@gnu.org \
--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).