From: Eli Zaretskii <eliz@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [PATCH] Keep network security info buffers after use
Date: Tue, 19 Dec 2023 14:51:21 +0200 [thread overview]
Message-ID: <83h6keicdy.fsf@gnu.org> (raw)
In-Reply-To: <87sf3ywxak.fsf@red-bean.com> (message from Karl Fogel on Mon, 18 Dec 2023 23:56:03 -0600)
> From: Karl Fogel <kfogel@red-bean.com>
> Cc: emacs-devel@gnu.org
> Date: Mon, 18 Dec 2023 23:56:03 -0600
>
> I'm still waiting to hear if there is approval for, or concern
> about, the idea of letting `C-x o' depart (presumably temporarily)
> from a `read-multiple-choice' prompt.
I think read-multiple-choice is intentionally programmed to implement
a modal dialog. That's why "C-x o" is disallowed.
Once again, I think a special command for getting the cert info is the
best solution to your problem: it is relatively simple, it is
unintrusive, and it doesn't affect functionalities unrelated to that
particular problem. By contrast, making significant changes in rmc.el
just to cater to this use case sounds wrong to me.
next prev parent reply other threads:[~2023-12-19 12:51 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6keicdy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--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 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.