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

["Kévin Le Gouguec" <kevin.legouguec@gmail.com>]

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?

Sorry for butting in - no strong intuition re. what the better
UX/complexity tradeoff is between (a) letting the certificate buffers
linger after aborting (b) letting users enter recursive edits (TIL
that's a thing with rmc, neat) (c) adding a command to… do something.

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"

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.