Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
References: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
In-Reply-To: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
From: Jacob Lowe <jacoblowe2.0@gmail.com>
Date: Sat, 07 May 2016 16:43:37 +0000
Message-ID: <CAEyFG7a9mFztTteV=WPLmVCM3+dyXSU5wtv7KdgJyC65fNbvaw@mail.gmail.com>
Subject: Re: leading '=' in enviroment variable truncated
To: zsh-workers@zsh.org
Content-Type: multipart/alternative; boundary=94eb2c11c4c278c02d053243471a

--94eb2c11c4c278c02d053243471a
Content-Type: text/plain; charset=UTF-8

Sorry realized I sent this out missing a key piece of info. My current
version of *zsh is** 5.0.8 (x86_64-apple-darwin15.0)*. Also the last
example I posted spits out "test" not "FOO".

On Sat, May 7, 2016 at 9:21 AM Jacob Lowe <jacoblowe2.0@gmail.com> wrote:

> Hey all,
>
> First off thanks for making/maintaining ZSH. Its a awesome project, and
> has been my default shell for 3 plus years.
>
> I recently ran into a unique thing that ZSH does that cause a bug that was
> filed on a project I help maintain.
>
> https://github.com/motdotla/dotenv/issues/140
>
> It is a javascript module that loads environment variables into the
> process for the node program to use. I noticed the module was parsing the
> the env ok and the bug only occurred while preloading the script. I tried
> to load in the env via the command line straight into the node program as
> well.
>
> TEST='=FOO' node -e 'console.log(process.env.TEST)'
>
>
> This spits out "FOO" with no leading "=".
>
> So I filed and issue on nodejs repo thinking this had to do with the way
> it was handling the environment variables.
>
> https://github.com/nodejs/node/issues/6627
>
> From the feedback in the ticket, it seems this is happening in ZSH only
> and when logging into bash the command works as expected. I also tried
> something very similar in ruby and got the same result.
>
> TEST='=test' ruby -e 'puts ENV["TEST"]'
>
>
> This also spits out "FOO" with no leading "=".
>
> Is this intended behavior? and thanks again.
>

--94eb2c11c4c278c02d053243471a--