[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FW: setenv doesn't expand variable names in values
From: |
Marshall, Simon |
Subject: |
FW: setenv doesn't expand variable names in values |
Date: |
Thu, 22 Nov 2001 09:36:39 -0000 |
Hi folks, I'm forwarding this in case it isn't in a TODO list
somewhere...
Simon.
-----Original Message-----
From: address@hidden [mailto:address@hidden
Sent: 04 September 2001 16:51
To: Marshall, Simon
Cc: 'Emacs Pretest Bug'
Subject: Re: setenv doesn't expand variable names in values
"Marshall, Simon" <address@hidden> writes:
> I tried to use M-x setenv to prepend a directory to $PATH with
something
> like:
>
> M-x setenv RET PATH RET /some/path:$PATH RET
>
> only to find that it didn't do what I expected---M-x setenv didn't
> expand the $PATH in the variable value.
>
> This seems like a misfeature to me---I can't think of a reason why it
> would be useful to not expand variables in values. If I were to use
csh
> or tcsh setenv it would expand it.
>
> So, I suggest that variables in values are expanded.
>
> I also suggest that setenv return its value arg. At the moment it
> returns various different types of things depending on what happens.
I think that's a good feature, for 21.2. For now, I've just fixed a
bug in setenv which advertized to add something to the mini-buffer
history which it didn't.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- FW: setenv doesn't expand variable names in values,
Marshall, Simon <=