From: Eli Zaretskii <eliz@gnu.org>
To: dick.r.chiang@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 61244@debbugs.gnu.org
Subject: bug#61244: 30.0.50; [PATCH] Promote called-interactively-p
Date: Fri, 03 Feb 2023 09:35:41 +0200 [thread overview]
Message-ID: <83y1pfuroy.fsf@gnu.org> (raw)
In-Reply-To: <87sffnzrbj.fsf@dick> (dick.r.chiang@gmail.com)
> From: dick.r.chiang@gmail.com
> Date: Thu, 02 Feb 2023 16:32:32 -0500
>
> FUD surrounding `called-interactively-p` continues to saddle
> functions with an incongruous "interactive-p" optional
> argument. `called-interactively-p` is safe enough, and if not,
> no one is going to miss whatever trivial behaviors hinge
> on its correctness.
Please explain the rationale and the effects of the code in more
detail, otherwise this is impossible to consider.
Stefan, any comments or insights?
next prev parent reply other threads:[~2023-02-03 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 21:32 bug#61244: 30.0.50; [PATCH] Promote called-interactively-p dick.r.chiang
2023-02-03 7:35 ` Eli Zaretskii [this message]
2023-02-03 15:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83y1pfuroy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61244@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--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).