From: Sean Whitton <spwhitton@spwhitton.name>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master a30781399b3: * subr-x (eval-command-interactive-spec): New function.
Date: Fri, 16 Jun 2023 08:12:11 +0100 [thread overview]
Message-ID: <87ttv7519w.fsf@melete.silentflame.com> (raw)
In-Reply-To: <jwvilbp4vmk.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 14 Jun 2023 16:52:37 -0400")
Hello,
On Wed 14 Jun 2023 at 04:52PM -04, Stefan Monnier wrote:
> OK, so that's one example. Any other? Because, to me, a single
> use-case doesn't seem to justify the definition of a one-liner helper
> function.
> [ Especially since that helper function is still not a faithful
> simulation of what happens in a "normal" execution of the command
> and fixing that wrinkle will likely require changing the API :-( ]
Right. I don't have another example yet, and I don't think I would have
proposed adding this at all had I realised that most of it is already
implemented in `interactive-form'. If no-one else speaks up in favour
of keeping it, I'll go ahead and remove it again.
--
Sean Whitton
next prev parent reply other threads:[~2023-06-16 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168595059426.2523.2109338263713299231@vcs2.savannah.gnu.org>
[not found] ` <20230605073635.19060C00613@vcs2.savannah.gnu.org>
2023-06-05 10:24 ` master a30781399b3: * subr-x (eval-command-interactive-spec): New function Philip Kaludercic
2023-06-06 11:10 ` Sean Whitton
2023-06-06 11:25 ` Mattias Engdegård
2023-06-05 16:14 ` Stefan Monnier
2023-06-06 11:18 ` Sean Whitton
2023-06-09 14:39 ` Stefan Monnier
2023-06-14 10:14 ` Sean Whitton
2023-06-14 20:52 ` Stefan Monnier
2023-06-16 7:12 ` Sean Whitton [this message]
2023-06-05 11:40 Eli Zaretskii
2023-06-06 11:10 ` Sean Whitton
2023-06-06 11:59 ` Eli Zaretskii
2023-06-14 10:18 ` Sean Whitton
2023-06-14 11:35 ` Eli Zaretskii
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=87ttv7519w.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=emacs-devel@gnu.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 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).