From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Christoph Scholtes <cschol2112@googlemail.com>, emacs-devel@gnu.org
Subject: Re: exec-path and PATH
Date: Sun, 20 Mar 2011 22:44:11 +0000 [thread overview]
Message-ID: <87zkops98k.fsf@gmail.com> (raw)
In-Reply-To: <838vw9a5qt.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Mar 2011 22:36:58 +0200")
Hi Eli,
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Christoph Scholtes <cschol2112@googlemail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sun, 20 Mar 2011 13:45:50 -0600
>>
>> However, now I wonder why we have a facility like exec-path at
>> all. Wouldn't the process-environment's PATH be enough?
>
> Because working with a list is much easier than with a single string?
From the user perspective - yes.
We could have a module to handle operations on PATH which would include
a function to append/prepend a list of paths and then start some
function or code with a path set-up. I know this would be a major change
though. Other solution is exec-path to be just additional set of the
directories that we pre-pend to the PATH. In both cases however we'd
lose ability to amend the environment which might be not desirable I
agree.
Thanks,
Wojciech
next prev parent reply other threads:[~2011-03-20 22:44 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkops98k.fsf@gmail.com \
--to=wojciech.meyer@googlemail.com \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.