all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Hanchrow <eric.hanchrow@gmail.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 13:46:18 -0700	[thread overview]
Message-ID: <AANLkTi=rrafocFcbWaew-gfnG_KmV4romn=OdVyD0Qr1@mail.gmail.com> (raw)
In-Reply-To: <838vw9a5qt.fsf@gnu.org>

On Sun, Mar 20, 2011 at 1:36 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> 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?

That would argue for making "exec-path" a sort of magical variable --
one whose value changes all by itself, whenever the PATH environment
variable changes.  Would that be feasible?



  reply	other threads:[~2011-03-20 20:46 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=rrafocFcbWaew-gfnG_KmV4romn=OdVyD0Qr1@mail.gmail.com' \
    --to=eric.hanchrow@gmail.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.