Re: [PATCH] Keep network security info buffers after use

[Eli Zaretskii]

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Karl Fogel <kfogel@red-bean.com>,  stefankangas@gmail.com,
>   emacs-devel@gnu.org
> Date: Mon, 25 Dec 2023 18:35:45 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Karl Fogel <kfogel@red-bean.com>
> >> Cc: Stefan Kangas <stefankangas@gmail.com>,  emacs-devel@gnu.org
> >> Date: Sun, 24 Dec 2023 10:34:32 -0500
> >> 
> >> "The inspection" can be an arbitrarily complex process, during 
> >> which the user should have all the usual power of Emacs available.
> >
> > You always have the possibility of aborting the connection with C-g
> > and then doing all those arbitrarily complex processes.
> 
> But C-g dismisses the *Certificate Details* buffer, so that makes an
> "arbitrarily complex" inspection somewhat hard to proceed with?

Who said that those complex processes need those details?  No
specifics were brought up about those complex processes, so we are all
basically waving hands, and each one of us has some different mental
picture about what's involved.  This doesn't tend to lead towards
effective discussion with any useful outcome.

> All I can say is that the first time I met this prompt, my reflexes were
> 
> * C-x o                 - "Ah, right; rmc, can't do that"
> * C-g; C-x b Cert TAB   - "Oh, drats; the buffer was killed"

I guess you haven't read the prompt, because my reflex was to type 'd'
and read there.

> So FWIW (a) would have had my vote, and FWIW² I'd have been fine with it
> being optional & off by default.  But now that I know about rmc
> leveraging query-replace-map and the C-r escape hatch, no strong
> opinion.

Thanks for sharing, so I guess your personal conclusion is that
nothing needs to be done, yes?