From: Milan Zimmermann <milan.zimmermann@gmail.com>
To: 59469@debbugs.gnu.org
Subject: bug#59469: Adding a simpler duplication of the issue
Date: Mon, 21 Nov 2022 21:50:03 -0500 [thread overview]
Message-ID: <CAEc2VK0yJf_2S88WSRtiSoXGQkW2jHVJCYmQsH+3sAvFHrAANA@mail.gmail.com> (raw)
In-Reply-To: <CAEc2VK05DZQipoBrHVqcVewuXiZbPRyCGJ1m2hvvwEeYksD=1A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
A simpler duplication shows the issue is below.
It appears the issue is is not related to the "for loop" - it can be
duplicated just writing code inside the eshell { .. } block.
To duplicate, please create a file ccc.el.gz - something the gzip does not
fail on.
Then, On the eshell prompt, enter the following code:
$ export aaa="This is contents of aaa"
{
# create a variable in this block
export bbb=$aaa;
echo "Before gzip: aaa=$aaa"
echo "Before gzip: bbb=$bbb";
gzip --decompress ccc.el.gz;
echo "After gzip: aaa=$aaa"
echo "After gzip: bbb=$bbb";
}
Before gzip: aaa=This is contents of aaa
Before gzip: bbb=This is contents of aaa
After gzip: aaa=This is contents of aaa
After gzip: bbb=nil
$
Same bug: After the call to non-elisp program, /usr/bin/gzip, a previously
exported variable bbb (exported inside the block) is nullified.
Thanks
[-- Attachment #2: Type: text/html, Size: 1283 bytes --]
next prev parent reply other threads:[~2022-11-22 2:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 2:04 bug#59469: 29.0.50; Eshell "for" loop: Calling a non-lisp command (example: /usr/bin/tail) sets the variable exported in the {} block of "for var in list {}" to nil Milan Zimmermann
2022-11-22 2:50 ` Milan Zimmermann [this message]
2022-11-22 4:56 ` bug#59469: Adding a simpler duplication of the issue Jim Porter
2022-11-22 7:18 ` Milan Zimmermann
2023-01-25 1:39 ` Jim Porter
2023-01-29 6:55 ` bug#59469: 29.0.50; Eshell "for" loop: Calling a non-lisp command (example: /usr/bin/tail) sets the variable exported in the {} block of "for var in list {}" to nil (was: Adding a simpler duplication of the issue) Jim Porter
2023-02-10 5:44 ` Jim Porter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEc2VK0yJf_2S88WSRtiSoXGQkW2jHVJCYmQsH+3sAvFHrAANA@mail.gmail.com \
--to=milan.zimmermann@gmail.com \
--cc=59469@debbugs.gnu.org \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).