From: Karl Fogel <kfogel@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Keep network security info buffers after use
Date: Tue, 19 Dec 2023 14:18:52 -0600 [thread overview]
Message-ID: <87o7emosib.fsf@red-bean.com> (raw)
In-Reply-To: <83wmtaggdq.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Dec 2023 21:08:01 +0200")
On 19 Dec 2023, Eli Zaretskii wrote:
>> From: Karl Fogel <kfogel@red-bean.com>
>> Cc: rms@gnu.org, emacs-devel@gnu.org
>> Date: Tue, 19 Dec 2023 12:57:04 -0600
>>
>> How about an option that allows `C-x o' to escape from the
>> modal
>> dialog of `read-multiple-choice'?
>
>That dialog was AFAIU intentionally designed not to allow any
>such
>escapes.
>
>Once again: let's fix the particular problem you had, and that
>problem
>was not with read-multiple-choice.
Fixing (i.e., reducing) the strictness of Emacs's
`read-multiple-choice' modal dialog would be worth the effort for
me. However, you don't agree that the current strictness is a
problem.
Meanwhile, implementing a mechanism (re)display the cert info from
`nsm-query-user' is not worth the effort for me (maybe someone
else might find it worth doing). It's already quite rare that
users are even presented with cert info; it would be even more
rare that a user who is presented with that info then takes the
steps needed to discover that there's a way to redisplay the cert
info (heck, very few users even check certs in the first place --
most people just hit "a"ccept at the prompt and continue). The
ratio of effort to user's-lives-improved is not high enough to
cross the implementation threshold for me here.
Thanks for talking through the possibilities. We disagree about
modal dialog behavior, but being maintainer means making decisions
sometimes, and it's helpful that you've made one here.
Best regards,
-Karl
next prev parent reply other threads:[~2023-12-19 20:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 19:02 [PATCH] Keep network security info buffers after use Karl Fogel
2023-12-17 19:27 ` Eli Zaretskii
2023-12-17 23:27 ` Karl Fogel
2023-12-18 17:36 ` Eli Zaretskii
2023-12-19 0:00 ` Karl Fogel
2023-12-19 5:31 ` tomas
2023-12-19 12:34 ` Eli Zaretskii
2023-12-19 12:50 ` tomas
2023-12-19 13:05 ` Eli Zaretskii
2023-12-20 22:43 ` Andreas Schwab
2023-12-21 6:45 ` Eli Zaretskii
2023-12-17 21:03 ` Andreas Schwab
2023-12-19 3:49 ` Richard Stallman
2023-12-19 5:56 ` Karl Fogel
2023-12-19 12:51 ` Eli Zaretskii
2023-12-19 13:10 ` tomas
2023-12-19 18:57 ` Karl Fogel
2023-12-19 19:08 ` Eli Zaretskii
2023-12-19 20:18 ` Karl Fogel [this message]
2023-12-20 21:34 ` Jens Schmidt
2023-12-20 22:26 ` Andreas Schwab
2023-12-21 6:29 ` Eli Zaretskii
2023-12-21 17:38 ` Karl Fogel
2023-12-21 18:43 ` Andreas Schwab
2023-12-21 23:10 ` Karl Fogel
2023-12-22 7:29 ` Eli Zaretskii
2023-12-22 10:00 ` Stefan Kangas
2023-12-22 11:51 ` Eli Zaretskii
2023-12-22 21:58 ` Jens Schmidt
2023-12-22 22:10 ` Jens Schmidt
2023-12-23 7:15 ` Eli Zaretskii
2023-12-23 10:46 ` Jens Schmidt
2023-12-23 22:57 ` Karl Fogel
2023-12-24 6:14 ` Eli Zaretskii
2023-12-24 13:52 ` Stefan Kangas
2023-12-24 14:51 ` Eli Zaretskii
2023-12-24 15:34 ` Karl Fogel
2023-12-24 16:28 ` Eli Zaretskii
2023-12-25 17:35 ` Kévin Le Gouguec
2023-12-25 18:51 ` Eli Zaretskii
2023-12-25 20:23 ` Tomas Hlavaty
2023-12-26 14:43 ` Kévin Le Gouguec
2023-12-26 17:01 ` Eli Zaretskii
2023-12-26 22:09 ` Stefan Kangas
2023-12-27 12:54 ` Eli Zaretskii
2023-12-25 20:18 ` Tomas Hlavaty
2023-12-27 12:35 ` Eli Zaretskii
2023-12-24 18:42 ` [External] : " Drew Adams
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=87o7emosib.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).