From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: larsi@gnus.org, 54190@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#54190: 29.0.50; [PATCH] Incorrect/missing documentation for some Eshell "$" syntaxes
Date: Fri, 04 Mar 2022 09:16:44 +0200 [thread overview]
Message-ID: <83k0dai3vn.fsf@gnu.org> (raw)
In-Reply-To: <797bb243-5397-bb8f-0902-7f96273e913f@gmail.com> (message from Jim Porter on Thu, 3 Mar 2022 21:55:41 -0800)
> Cc: larsi@gnus.org, 54190@debbugs.gnu.org, monnier@iro.umontreal.ca
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Thu, 3 Mar 2022 21:55:41 -0800
>
> After a bit of looking at the `eshell-do-eval' implementation, I
> realized that there's a better solution that's very simple. See the
> attached patch. It's simple enough that it might be fine for Emacs 28,
> but the existing change on the 28 branch is probably a bit safer, since
> that change was just a partial revert. I'm not aware of anything that
> could be broken by this new patch, but you never know...
Thanks, I think this should be installed on master.
next prev parent reply other threads:[~2022-03-04 7: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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k0dai3vn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54190@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.