From: David Hedbor <david@hedbor.org>
To: zsh-users@math.gatech.edu
Subject: Patch for the previous bug
Date: 05 Jun 1998 17:53:27 -0700 [thread overview]
Message-ID: <86iumf9wqg.fsf@animearchive.org> (raw)
This patch fixes the problem I reported earlier. If it's the desired
way to do it or not, I don't know. :-)
*** builtin.c Fri Jun 5 17:48:52 1998
--- builtin.c~ Sun May 31 03:26:12 1998
***************
*** 1587,1592 ****
if (PM_TYPE(pm->flags) != PM_ARRAY) {
if (pm->flags & PM_EXPORTED) {
! if (!pm->env && (asg->value || getsparam(asg->name)))
! pm->env = addenv(asg->name, (asg->value) ? asg->value : getsparam(asg->name));
} else if (pm->env) {
delenv(pm->env);
--- 1587,1592 ----
if (PM_TYPE(pm->flags) != PM_ARRAY) {
if (pm->flags & PM_EXPORTED) {
! if (!pm->env)
! pm->env = addenv(asg->name, (asg->value) ? asg->value : getsparam(asg->name));
} else if (pm->env) {
delenv(pm->env);
--
David Hedbor
reply other threads:[~1998-06-06 0:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86iumf9wqg.fsf@animearchive.org \
--to=david@hedbor.org \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).