From: Eli Zaretskii <eliz@gnu.org>
To: monnier@iro.umontreal.ca, sbaugh@janestreet.com
Cc: larsi@gnus.org, 67837@debbugs.gnu.org
Subject: bug#67837: 29.1.90; inhibit-interaction breaks keyboard macros
Date: Sat, 17 Feb 2024 16:43:20 +0200 [thread overview]
Message-ID: <86le7jtalz.fsf@gnu.org> (raw)
In-Reply-To: <86r0hbtayp.fsf@gnu.org> (message from Eli Zaretskii on Sat, 17 Feb 2024 16:35:42 +0200)
> Cc: sbaugh@janestreet.com, larsi@gnus.org, 67837@debbugs.gnu.org
> Date: Sat, 17 Feb 2024 16:35:42 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > More specifically, have you ever seen or heard about a piece of code
> > using `inhibit-interaction`? I have not, *except* in the context of
> > bugs like this one. IOW, AFAICT, `inhibit-interaction` fails at
> > providing the only feature for which it's useful.
>
> See bug#13697, which was the motivation for introducing this variable.
> It mentions a couple of use cases, bug#6567 and bug#25214.
Btw, I'm perfectly fine if we want to decide that the
inhibit-interaction experiment failed, and remove it from Emacs. If
you are right, and no one uses it out there yet, doing so will not
cause any harm. We could then reopen the above bug, and either close
it as wontfix or wait for a better solution to present itself.
next prev parent reply other threads:[~2024-02-17 14:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 16:48 bug#67837: 29.1.90; inhibit-interaction breaks keyboard macros Spencer Baugh
2023-12-15 16:50 ` Spencer Baugh
2023-12-15 18:54 ` Eli Zaretskii
2023-12-15 19:48 ` Spencer Baugh
2023-12-15 20:01 ` Eli Zaretskii
2023-12-15 20:09 ` Spencer Baugh
2023-12-16 7:02 ` Eli Zaretskii
2023-12-16 13:22 ` sbaugh
2023-12-16 13:57 ` Eli Zaretskii
2023-12-15 20:14 ` Eli Zaretskii
2023-12-15 20:39 ` Spencer Baugh
2023-12-16 7:14 ` Eli Zaretskii
2023-12-16 15:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-16 16:08 ` Eli Zaretskii
2023-12-16 17:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-16 22:26 ` Spencer Baugh
2024-02-16 23:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 7:53 ` Eli Zaretskii
2024-02-17 14:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 14:35 ` Eli Zaretskii
2024-02-17 14:43 ` Eli Zaretskii [this message]
2024-02-17 15:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-17 16:07 ` Eli Zaretskii
2024-02-17 7:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86le7jtalz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67837@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.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 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.