[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: exec-path and PATH
From: |
Eric Hanchrow |
Subject: |
Re: exec-path and PATH |
Date: |
Sun, 20 Mar 2011 13:46:18 -0700 |
On Sun, Mar 20, 2011 at 1:36 PM, Eli Zaretskii <address@hidden> 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?
- exec-path and PATH, Christoph Scholtes, 2011/03/18
- Re: exec-path and PATH, Eli Zaretskii, 2011/03/19
- Re: exec-path and PATH, Christoph Scholtes, 2011/03/19
- Re: exec-path and PATH, Eli Zaretskii, 2011/03/19
- Re: exec-path and PATH, Christoph Scholtes, 2011/03/19
- Re: exec-path and PATH, Eli Zaretskii, 2011/03/19
- Re: exec-path and PATH, Christoph Scholtes, 2011/03/20
- Re: exec-path and PATH, Eli Zaretskii, 2011/03/20
- Re: exec-path and PATH,
Eric Hanchrow <=
- Re: exec-path and PATH, Eric Schulte, 2011/03/21
- Re: exec-path and PATH, Wojciech Meyer, 2011/03/20
Re: exec-path and PATH, Christoph Scholtes, 2011/03/19
Re: exec-path and PATH, Eli Zaretskii, 2011/03/19
Re: exec-path and PATH, Stefan Monnier, 2011/03/19