From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 53293@debbugs.gnu.org
Subject: bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external
Date: Thu, 20 Jan 2022 13:48:26 +0200 [thread overview]
Message-ID: <83y23apr05.fsf@gnu.org> (raw)
In-Reply-To: <632df5ab-007a-d859-fea6-89861c03ff1c@gmail.com> (message from Jim Porter on Wed, 19 Jan 2022 19:13:33 -0800)
> From: Jim Porter <jporterbugs@gmail.com>
> Cc: 53293@debbugs.gnu.org
> Date: Wed, 19 Jan 2022 19:13:33 -0800
>
> While it would probably make sense to wait a bit longer to see if anyone
> has comments on my audit of the existing Eshell built-in commands, I've
> implemented the first two points here (not "echo -e", though).
Thanks, LGTM.
> The changes to `source' and `.' might warrant a NEWS entry, since it's a
> (small) incompatible change; however, I think it's so rare that someone
> would call "source --help" that it might not be worth adding to NEWS.
> I'll do whatever others think is best here, though.
I think a NEWS entry is called for, since the change in behavior is
not backward-compatible.
next prev parent reply other threads:[~2022-01-20 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 4:03 bug#53293: 29.0.50; [PATCH] `eshell-eval-using-options' should report error for unrecognized option, even with no :external Jim Porter
2022-01-16 9:04 ` Eli Zaretskii
2022-01-16 20:31 ` Jim Porter
2022-01-20 3:13 ` Jim Porter
2022-01-20 11:48 ` Eli Zaretskii [this message]
2022-01-21 4:00 ` Jim Porter
2022-01-21 12:07 ` Lars Ingebrigtsen
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=83y23apr05.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53293@debbugs.gnu.org \
--cc=jporterbugs@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 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).