[bug] problem with env vars that zsh sets itself

[bug] problem with env vars that zsh sets itself

[Stephane Chazelas]

zsh's "export" command doesn't list the environment variables
that zsh sets itself.

$ env -i zsh -xc 'export;env'
+zsh:1> export
+zsh:1> env
HOME=/home/stephane
LOGNAME=stephane
SHLVL=0
PWD=/home/stephane
OLDPWD=/home/stephane
_=/usr/bin/env

Actually, it's as if they were not given the "export" flag even
though they are passed to the environment of executed commands:

$ env -i zsh -c 'typeset -p HOME SHLVL'
typeset HOME=/home/stephane
typeset -i10 SHLVL=1

$ zsh --version
zsh 5.2 (x86_64-debian-linux-gnu)

Seems to be a regression. It used to work OK in 4.1.1

-- 
Stephane

Re: [bug] problem with env vars that zsh sets itself

[Peter Stephenson]

On Fri, 30 Sep 2016 09:55:38 +0100
Stephane Chazelas <stephane.chazelas@gmail.com> wrote:
> zsh's "export" command doesn't list the environment variables
> that zsh sets itself.

diff --git a/Src/params.c b/Src/params.c
index 8271a8b..e115102 100644
--- a/Src/params.c
+++ b/Src/params.c
@@ -4727,6 +4727,7 @@ addenv(Param pm, char *value)
      if (pm->env)
          zsfree(pm->env);
      pm->env = newenv;
+     pm->node.flags |= PM_EXPORTED;
 #else
     /*
      * Under Cygwin we must use putenv() to maintain consistency.

pws