From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tomas Hlavaty Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Keep network security info buffers after use Date: Mon, 25 Dec 2023 21:18:53 +0100 Message-ID: <87zfxyavde.fsf@neko.mail-host-address-is-not-set> References: <87plz4irev.fsf@red-bean.com> <83frzufo9x.fsf@gnu.org> <838r5jd56w.fsf@gnu.org> <87mstzwr5j.fsf@red-bean.com> <834jg7d0p2.fsf@gnu.org> <87h6k6chhq.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36602"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Karl Fogel , stefankangas@gmail.com, emacs-devel@gnu.org To: =?utf-8?Q?K=C3=A9vin?= Le Gouguec , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 25 21:20:23 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 1rHrR0-0009MU-Ve for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Dec 2023 21:20:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHrPh-0001rl-Po; Mon, 25 Dec 2023 15:19:01 -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 1rHrPg-0001rU-AB for emacs-devel@gnu.org; Mon, 25 Dec 2023 15:19:00 -0500 Original-Received: from logand.com ([37.48.87.44]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rHrPe-0002SI-TN; Mon, 25 Dec 2023 15:19:00 -0500 Original-Received: by logand.com (Postfix, from userid 1001) id 5DFE419E841; Mon, 25 Dec 2023 21:18:56 +0100 (CET) X-Mailer: emacs 28.2 (via feedmail 11-beta-1 I) In-Reply-To: <87h6k6chhq.fsf@gmail.com> Received-SPF: pass client-ip=37.48.87.44; envelope-from=tom@logand.com; helo=logand.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:314221 Archived-At: On Mon 25 Dec 2023 at 18:35, K=C3=A9vin Le Gouguec wrote: > 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=E2=80=A6 do someth= ing. another option: There should not be modal UI that constrains my options vi-style. The whole process is sequential so it could display the information in the same output buffer, and clear the buffer at the beginning of each step. > * C-x o - "Ah, right; rmc, can't do that" > * C-g; C-x b Cert TAB - "Oh, drats; the buffer was killed" i find it also very frustrating