Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [bug] problem with env vars that zsh sets itself
- X-seq: zsh-workers 39519
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: [bug] problem with env vars that zsh sets itself
- Date: Fri, 30 Sep 2016 11:09:32 +0100
- Cms-type: 201P
- In-reply-to: <20160930085538.GA12137@chaz.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
- Organization: Samsung Cambridge Solution Centre
- References: <CGME20160930095458eucas1p29d154e52d3afbbd3d4dd5c6185593af6@eucas1p2.samsung.com> <20160930085538.GA12137@chaz.gmail.com>
On Fri, 30 Sep 2016 09:55:38 +0100
Stephane Chazelas <stephane.chazelas@xxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author