From: Christoph Scholtes <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: exec-path and PATH
Date: Sun, 20 Mar 2011 13:45:50 -0600 [thread overview]
Message-ID: <86vczdeftd.fsf@gmail.com> (raw)
In-Reply-To: <83pqpmakt0.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 19 Mar 2011 22:59:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> PATH in process-environment is not used within Emacs except to pass it
> to sub-processes. Why would we want to restore its value after the
> sub-process exits?
Sorry Eli. This was my mistake. I was under the wrong impression that
Emacs worked with the OS's PATH directly and not with its own copy of
it. After looking at process-environment and the setenv function
documentation I see how it works.
However, now I wonder why we have a facility like exec-path at
all. Wouldn't the process-environment's PATH be enough?
(start|call)-process could look at PATH directly instead of
exec-path. This would also solve the problem of having to keep two
separate path collections (PATH and exec-path) up to date.
I saw that quite a few functions use exec-path, so I am not necessarily
suggesting to change it. I am just curious.
Christoph
next prev parent reply other threads:[~2011-03-20 19:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 3:19 exec-path and PATH Christoph Scholtes
2011-03-19 8:10 ` Eli Zaretskii
2011-03-19 16:36 ` Christoph Scholtes
2011-03-19 17:26 ` Eli Zaretskii
2011-03-19 19:50 ` Christoph Scholtes
2011-03-19 20:59 ` Eli Zaretskii
2011-03-20 19:45 ` Christoph Scholtes [this message]
2011-03-20 20:36 ` Eli Zaretskii
2011-03-20 20:46 ` Eric Hanchrow
2011-03-21 14:04 ` Eric Schulte
2011-03-20 22:44 ` Wojciech Meyer
2011-03-19 16:49 ` Christoph Scholtes
2011-03-19 17:18 ` PJ Weisberg
2011-03-19 17:23 ` Christoph Scholtes
2011-03-19 18:52 ` Harald Hanche-Olsen
2011-03-20 2:53 ` Stefan Monnier
2011-03-19 17:43 ` Eli Zaretskii
2011-03-20 2:50 ` Stefan Monnier
2011-03-20 6:34 ` 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=86vczdeftd.fsf@gmail.com \
--to=cschol2112@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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).