[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: setenv's broken case when value is nil

From: Stefan Monnier
Subject: Re: setenv's broken case when value is nil
Date: Thu, 18 Feb 2010 10:38:41 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux)

>> address@hidden changed env.el on 2007-08-29 to define setenv-internal and
>> for setenv always to keep the variable name in process-environment, even if
>> value is nil.  In other words, he removed the distinction between the empty
>> string and nil, and therefore you can't remove variables from the
>> environment using setenv anymore.

That would be a bug, so bug-gnu-emacs would have been a better place to
send it.
This said, I don't see this bug: after (setenv "COLORTERM" nil),
a M-! printenv RET indeed doesn't show COLORTERM any more.

`process-environment' still has an entry for COLORTERM but this entry
has the form "COLORTERM" rather than "COLORTERM=" which distinguishes
the empty-string-envvars from the the absent-envvars.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]