From: Jim Porter <jporterbugs@gmail.com>
To: Milan Zimmermann <milan.zimmermann@gmail.com>, 59612@debbugs.gnu.org
Subject: bug#59612: 29.0.50; Eshell: The behavior of conditionals depends on whitespace
Date: Sat, 26 Nov 2022 10:42:42 -0800 [thread overview]
Message-ID: <8fec9d79-4118-eaa5-b762-c57f11f41aef@gmail.com> (raw)
In-Reply-To: <CAEc2VK1jY+e4Vt1HFRxxeW-AehSqYTWJNd=g2S99FBqPgx=Y8g@mail.gmail.com>
On 11/26/2022 7:52 AM, Milan Zimmermann wrote:
> # Result:
> # "It is 3"
> # "It is NOT 3"
> #
>
> if { = 3 3 } {
> echo "It is 3"
> }
> {
> echo "It is NOT 3"
> }
According to Eshell's logic, I think this is correct (though
inconvenient). Because Eshell treats a newline as the end of a command
whenever possible, it just sees these as two separate commands.
> # BUT we get the same incorrect result if we place the whole if
> expression into {}
> {
> if { = 4 4 } {
> echo "It is 4"
> }
> {
> echo "It is NOT 4"
> }
> }
This is really the same as the above: {...} allows multiple commands, so
it sees this as two separate commands nested inside the {}.
Ultimately, I think this is closer to a feature request: adding an
"else" token would disambiguate this:
if { = 2 2 } {
echo "good"
}
else {
echo "bad"
}
Actually making this work in Eshell's internals might be painful though...
I do also see a potential bug. I'd expect this to work, but it doesn't:
if { = 2 2 } \
{ echo "good" } \
{ echo "bad" }
next prev parent reply other threads:[~2022-11-26 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 15:52 bug#59612: 29.0.50; Eshell: The behavior of conditionals depends on whitespace Milan Zimmermann
2022-11-26 15:59 ` bug#59612: A comment line in example change Milan Zimmermann
2022-11-26 16:19 ` bug#59612: Incorrect behavior also with ${CONDITION} Milan Zimmermann
2022-11-26 18:28 ` Jim Porter
2022-11-26 19:32 ` Jim Porter
2022-11-26 18:42 ` Jim Porter [this message]
2022-11-27 0:39 ` bug#59612: 29.0.50; Eshell: The behavior of conditionals depends on whitespace Jim Porter
2022-11-27 2:16 ` Milan Zimmermann
2022-11-27 3:13 ` Jim Porter
2022-11-27 5:07 ` Milan Zimmermann
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=8fec9d79-4118-eaa5-b762-c57f11f41aef@gmail.com \
--to=jporterbugs@gmail.com \
--cc=59612@debbugs.gnu.org \
--cc=milan.zimmermann@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.