From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefankangas@gmail.com, kfogel@red-bean.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Keep network security info buffers after use
Date: Sat, 23 Dec 2023 11:46:51 +0100 [thread overview]
Message-ID: <06c025f5-741b-49f1-9b99-7ab4de05dfea@vodafonemail.de> (raw)
In-Reply-To: <837cl5fkye.fsf@gnu.org>
On 2023-12-23 08:15, Eli Zaretskii wrote:
>> 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?
With my (possibly limited) imagination I cannot see from where you
would get that information that you would like to display *after* the
fetch/logon/connection attempt has completed. Other than by storing
it unconditionally in some temporary or log-like buffer, which I
understand is also off-limits to you.
> 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?
My patch does not touch rmc.el, and I thought *that* was your main/only
concern.
next prev parent reply other threads:[~2023-12-23 10:46 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
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 [this message]
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=06c025f5-741b-49f1-9b99-7ab4de05dfea@vodafonemail.de \
--to=jschmidt4gnu@vodafonemail.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kfogel@red-bean.com \
--cc=stefankangas@gmail.com \
/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).