Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160508191448.ZM11069@torch.brasslantern.com>
Date: Sun, 8 May 2016 19:14:48 -0700
In-Reply-To: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
Comments: In reply to Jacob Lowe <jacoblowe2.0@gmail.com>
        "leading '=' in enviroment variable truncated" (May  7,  4:21pm)
References: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
To: zsh-workers@zsh.org, zsh-workers@zsh.org
Subject: Re: leading '=' in enviroment variable truncated
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On May 7,  4:21pm, Jacob Lowe wrote:
}
} 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"]'

Peter's discovery that this is a documented feature of iOS / OSX "setenv"
points to the obvious workaround:

TEST='==test' ruby -e 'puts ENV["TEST"]'


-- 
Barton E. Schaefer