From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: exec-path not changed in autostart
Date: Fri, 19 Dec 2014 23:46:10 +0200 [thread overview]
Message-ID: <83oaqzs47x.fsf@gnu.org> (raw)
In-Reply-To: <30a3109d-f2c6-4001-a761-8322133b4892@googlegroups.com>
> Date: Fri, 19 Dec 2014 13:09:19 -0800 (PST)
> From: Xin Jin <zariskij@gmail.com>
> Injection-Date: Fri, 19 Dec 2014 21:09:20 +0000
>
> I use the following code to add the paths from the shell environment to exec-path:
>
> (setq exec-path
> (append
> (split-string-and-unquote (getenv "PATH") ":")
> exec-path))
Why do you need that? exec-path already includes the directories from
$PATH, so the above sounds redundant.
next prev parent reply other threads:[~2014-12-19 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 21:09 exec-path not changed in autostart Xin Jin
2014-12-19 21:46 ` Eli Zaretskii [this message]
[not found] ` <mailman.16507.1419025590.1147.help-gnu-emacs@gnu.org>
2014-12-19 21:54 ` Xin Jin
2014-12-19 21:58 ` Xin Jin
2014-12-19 22:01 ` Xin Jin
2014-12-19 22:13 ` Óscar Fuentes
[not found] ` <mailman.16510.1419027237.1147.help-gnu-emacs@gnu.org>
2014-12-19 23:03 ` Xin Jin
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=83oaqzs47x.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).