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

[Eli Zaretskii]

> Date: Fri, 22 Dec 2023 22:58:38 +0100
> Cc: kfogel@red-bean.com, emacs-devel@gnu.org
> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> 
> > I agree that it could be useful in some cases.  Andreas suggested a
> > special command to show this information -- do you think this would be
> > a good solution for this situation?
> 
> I share Karl's opinion here that this could be too complex for the
> problem at hand.

Seriously? how is it more complex than what you propose below?  The
new command's body should basically be the same code as what you
propose to add.  (And adding an option not to kill the buffer,
something I proposed at the beginning, is even less complex: add a
defcustom, a single 'if', and an erase-buffer call.)

> How about the following variation of Karl's patch, which hopefully
> meets his request for simplicity and hopefully also these requests of
> yours (as long as you do not count the additional multiple choice
> option as something that must be revertable by option):

Your proposal will cause the mini-window be resized in many cases,
because your changes make the prompt wider than the (default) frame
width.  Thus, it will "punish" many people in many cases, although in
99% of cases this additional response is not needed.  So it's a step
in the wrong direction, from where I stand.

I can only suggest again to use one of the alternatives proposed
above.

P.S. I really don't understand this insistence on the original idea
that I said was unacceptable to me, where two acceptable alternatives
were already suggested.  Why not take one of those alternatives? why
keep pushing in the direction to which I said I object?