Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: leading '=' in enviroment variable truncated
- X-seq: zsh-workers 38418
- From: Jacob Lowe <jacoblowe2.0@xxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: leading '=' in enviroment variable truncated
- Date: Sat, 07 May 2016 16:43:37 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=DijMIJriw+x9jWDt9ALl9X08Pe/Xif0sdob/FAF38SI=; b=khuvLtr9uWdqazB9/20W9oxBWG7ktPZQmfnvfX0MC4LgoOAarhReUyL6qX8hbwC+L5 2tqy8mxrrZtkPKz49f8UX9OlOLsbgYmxQTtNaIQCyfHBKJ0cW2gjE26EvqRIS/yTdBqk qkSKGpnnFxDDh4heuZMCerzRspuEnl/XIt1tUYgAs1/kXoWydxBBGeTGEx0KMjLl43NH AnwGMcSWaSS/m7srDRJ6vfRhN0Gy/9jMmlKUD0hchLDyz84Ev0tfhL48OBPBt/RERSbO +i2NRuQGggQu+nJRktvp2zv9Sbvk8VKlTzsXKMQ42YIgQz3H7Sx4bfnNfwfgh/9ISFEY 5yhA==
- In-reply-to: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
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@xxxxxxxxx> 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.
>
Messages sorted by:
Reverse Date,
Date,
Thread,
Author