[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: Giorgos Keramidas
Subject: Re: setenv's broken case when value is nil
Date: Thu, 18 Feb 2010 06:12:43 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.92 (berkeley-unix)

On Wed, 17 Feb 2010 17:56:16 -0800 (PST), Noah Friedman <address@hidden> wrote:
> 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.
> Since all kinds of environment variables have meaning when they are
> defined, even if they are just set to the empty string, this is a screw.

It's not a very common usage pattern of environment variables, but you
are right.  There are all sorts of environment variables that work (for
some value of 'work') even if they are set to empty strings.

reply via email to

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