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: Fri, 22 Dec 2023 09:29:46 +0200 Message-ID: <83o7eig0et.fsf@gnu.org> References: <87plz4irev.fsf@red-bean.com> <87sf3ywxak.fsf@red-bean.com> <83h6keicdy.fsf@gnu.org> <87a5q6rpfj.fsf@red-bean.com> <83wmtaggdq.fsf@gnu.org> <87o7emosib.fsf@red-bean.com> <512a0684-f69c-4c7d-802f-274d4769426e@vodafonemail.de> <83a5q4gjaa.fsf@gnu.org> <87plyze9r4.fsf@red-bean.com> <87wmt78kgn.fsf@igel.home> <87cyuz6tja.fsf@red-bean.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21274"; mail-complaints-to="usenet@ciao.gmane.io" Cc: schwab@linux-m68k.org, jschmidt4gnu@vodafonemail.de, emacs-devel@gnu.org To: Karl Fogel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Dec 22 08:30:25 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 1rGZzF-0005JJ-Ls for ged-emacs-devel@m.gmane-mx.org; Fri, 22 Dec 2023 08:30:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rGZys-0004sM-DJ; Fri, 22 Dec 2023 02:30:02 -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 1rGZyq-0004rs-S3 for emacs-devel@gnu.org; Fri, 22 Dec 2023 02:30:00 -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 1rGZyp-00074K-Jz; Fri, 22 Dec 2023 02:29:59 -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=VGsoiPgjLcf6xaYZpoKgUseB2CYjGIQDKUYcIe5fh5A=; b=JTi81XeD1gfM PQc0wqJUrM1peStMq17/Ybp+kqo/F6GyPzR+/eWrReU0Sx8TG6sfaj/gPPy87FFhDL8rGogfLx9Fn 8j3qivfHebABvXhSF719COhvBzJP4ovqMA4h0bqNEQVhmQi0dvY0hlhY8KATqzqjgw7taHi/+WAka oHF2w7y3PdoNmcXJlCFfeUidKPD4RDkMywINaOPrcm9p5asHjtEPVjyx17vjkIn0qEbDtVdF2+l2z EHIymibpZZU8vHjGxnWWCkWtUHDn6KfSSonBLljjmmJP+sIHUMjrgY8IHjL+U7eoHR0CnMohJPVox Lx34bgn0UQ6mi9gqFj3iRg==; In-Reply-To: <87cyuz6tja.fsf@red-bean.com> (message from Karl Fogel on Thu, 21 Dec 2023 17:10:49 -0600) 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:314056 Archived-At: > From: Karl Fogel > Cc: Eli Zaretskii , Jens Schmidt > , emacs-devel@gnu.org > Date: Thu, 21 Dec 2023 17:10:49 -0600 > > On 21 Dec 2023, Andreas Schwab wrote: > > On Dez 21 2023, Karl Fogel wrote: > > > >> (The user already could do this by entering a recursive edit, > >> but that way > >> is much less familiar to many users than `C-x o' is.) > > > > Moving out of a short-form r-m-c requires entering a recursive > > edit, otherwise there would be nothing that executes the keys. > > Could we please establish first what we *want* the user experience > to be? In the case in point, where read-multiple-choice is invoked by nsm for the reasons of connection security, we _want_ the user to be able to respond with one of the provided single-key options, and with nothing else. > Obviously `read-multiple-choice' needs to keep the "read a key and > respond instantly" behavior that it has right now (in the calling > configuration used by `nsm-query-user', that is). To change that > UX would be a major regression, and I'm not proposing to change > it. I'm merely proposing that `C-x o' do what the user expects -- > because that key sequence is the obvious gateway to accomplishing > a thing the user sometimes wants to accomplish. If read-multiple-choice expects a single key, then we cannot allow "C-x o", because those are two keys, not one. > If it turns out that there's simply no way to implement this > behavior, then so be it -- I'll discover that when I go to > implement it. But generally it's possible to get Emacs to do what > we want. The question here is just determining what we want. read-multiple-choice _does_ have a way of accepting responses longer than one key -- that's what the LONG-FORM argument is for -- but that comes with a price, and in the case in point we don't want to pay that price. In other cases, if a non-modal dialog is desired, the caller should use LONG-FORM. > Take it on faith, for now, that we could make this happen. Let's > just discuss whether we *want* it, assuming we can have it. If we > decide we want it, I'll try to implement it, and I'll ask for help > if I don't see the way. If in the end we can't do it, fine, then > we would be in exactly the situation we're now anyway. You have already heard from me what we want (and I repeat that above). So I'm not sure why we still need to discuss that particular issue.