From: Tim Lewis <tim.lewis@insyde.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: [shell] Redirected Environment Variables Are Not Saved Correctly
Date: Fri, 2 Dec 2016 09:20:15 +0000 [thread overview]
Message-ID: <7236196A5DF6C040855A6D96F556A53F410DA5@msmail.insydesw.com.tw> (raw)
Test by doing this, immediately after booting:
Notice that echo has created a new environment variable _key to the value 4, But this variable does not show up when running "set"
Why? It is because the FileHandleWrappers does not use SetEnvironmentVariable. Instead, it tries to read and write the UEFI variable directly. But this method does not update the internal list of environment variables maintained by the Shell Protocol API.
This causes a lot of issues, because the results of any console redirection to an environment variable is not immediately visible.
Tim
[cid:image001.png@01D24C37.475327F0]
reply other threads:[~2016-12-02 9:20 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-list 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=7236196A5DF6C040855A6D96F556A53F410DA5@msmail.insydesw.com.tw \
--to=devel@edk2.groups.io \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox