From: Jim Porter <jporterbugs@gmail.com>
To: 54190@debbugs.gnu.org
Subject: bug#54190: 29.0.50; [PATCH] Incorrect/missing documentation for some Eshell "$" syntaxes
Date: Mon, 28 Feb 2022 00:16:21 -0800 [thread overview]
Message-ID: <1dfa575b-bf3f-84ca-b7b5-a612ffc57737@gmail.com> (raw)
In-Reply-To: <06a184d5-b191-4c63-a851-13d1c8c18eda@gmail.com>
On 2/27/2022 10:11 PM, Jim Porter wrote:
> Hmm, that's unfortunate. It seems that the "$<FOO>" syntax in Eshell
> broke sometime between 27.2 and 28. I'm bisecting to figure out where
> that happened, but figured I'd mention it now so there's no confusion if
> someone tries it out now on 28/29. Fix forthcoming (hopefully).
Ok, the breaking commit is b03f74e0f2a578b1580e8b1c368665850ee7f808
("Don't quote lambdas in several places"). Reverting the change in that
commit in lisp/eshell/esh-var.el fixes things, although I'm not sure why
yet. I believe that code gets evaluated by `eshell-do-eval', which
evaluates things in a very particular way in order to support deferring
evaluation at various points. Once I'm sure I understand why this is
breaking, I'll post a patch to fix the bustage.
next prev parent reply other threads:[~2022-02-28 8:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 21:34 bug#54190: 29.0.50; [PATCH] Incorrect/missing documentation for some Eshell "$" syntaxes Jim Porter
2022-02-28 6:11 ` Jim Porter
2022-02-28 8:16 ` Jim Porter [this message]
2022-02-28 9:38 ` Lars Ingebrigtsen
2022-02-28 13:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 13:28 ` Eli Zaretskii
2022-02-28 17:47 ` Jim Porter
2022-03-01 13:10 ` Eli Zaretskii
2022-03-04 5:55 ` Jim Porter
2022-03-04 7:16 ` Eli Zaretskii
2022-03-04 13:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-04 18:04 ` Jim Porter
2022-09-06 11:28 ` Lars Ingebrigtsen
2022-09-07 3:50 ` Jim Porter
2022-09-07 3:59 ` 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=1dfa575b-bf3f-84ca-b7b5-a612ffc57737@gmail.com \
--to=jporterbugs@gmail.com \
--cc=54190@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).