From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Keep network security info buffers after use Date: Sun, 24 Dec 2023 18:28:41 +0200 Message-ID: <834jg7d0p2.fsf@gnu.org> References: <87plz4irev.fsf@red-bean.com> <83frzufo9x.fsf@gnu.org> <838r5jd56w.fsf@gnu.org> <87mstzwr5j.fsf@red-bean.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27690"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 24 17:29:34 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rHRM5-00072h-QB for ged-emacs-devel@m.gmane-mx.org; Sun, 24 Dec 2023 17:29:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHRLM-00059j-UV; Sun, 24 Dec 2023 11:28:48 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rHRLL-00059Q-0p for emacs-devel@gnu.org; Sun, 24 Dec 2023 11:28:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rHRLK-0002tV-FP; Sun, 24 Dec 2023 11:28:46 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=IPquduknIjPJh3O2/5sxNbea3HtCLx60p0NZbmMjqcQ=; b=fFd0/lCRfQS0 DalGilagm2FPt6UAqo5bAgur7goygVxZaVK30+RECq/7txR4TmsUaMCYQNAj8RHUnW8QP1dJv+37d /QfsfWltB98x3fBQLrpiZ0vG2VIvC5Uqq/tAjtNeJqWidas/dbkUyHItkuGjS8Y6+GrRrKFAkh7gI czJJhgEijbc8aOrgmMRyLURvdORHMn+w2NjcJvKeMi44Ckp1Gu7QOKLCQI1RzxE0NHT21EAiZ4Prf u5U4nRTnq+W+3mc+Xja1BLkhHEuOQ47YssjjigWs58tem49xN8bc4lyTfr3uGxfQlk9DEf3++7u6M 205VZq+g7slaRTb9YpckYw==; In-Reply-To: <87mstzwr5j.fsf@red-bean.com> (message from Karl Fogel on Sun, 24 Dec 2023 10:34:32 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314136 Archived-At: > From: Karl Fogel > Cc: Stefan Kangas , 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. There's a limit to what a single command should allow as part of its supported workflow. Besides, if those processes take a long time, the connection will time out anyway. So I think by trying to cater to some insanely complex and very rare cases, we risk over-engineering this beyond any reason, and -- what's worse -- will complicate everybody's life where 99% of cases the life should be much simpler. Let's not do that.