From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Keep network security info buffers after use Date: Thu, 21 Dec 2023 11:38:39 -0600 Message-ID: <87plyze9r4.fsf@red-bean.com> 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> Reply-To: Karl Fogel Mime-Version: 1.0 Content-Type: text/plain; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18944"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Jens Schmidt , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 21 18:39:37 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 1rGN1E-0004jO-Pi for ged-emacs-devel@m.gmane-mx.org; Thu, 21 Dec 2023 18:39:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rGN0W-0007mS-VB; Thu, 21 Dec 2023 12:38:53 -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 1rGN0S-0007m9-Dl for emacs-devel@gnu.org; Thu, 21 Dec 2023 12:38:48 -0500 Original-Received: from sanpietro.red-bean.com ([45.79.25.59]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rGN0Q-0002mY-Bf; Thu, 21 Dec 2023 12:38:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=red-bean.com; s=202005newsp; h=Content-Type:MIME-Version:Message-ID:Date: Reply-To:References:In-Reply-To:Subject:Cc:To:From:Sender: Content-Transfer-Encoding:Content-ID:Content-Description; bh=1iPRkvOh46O6j0hcQIPn5u7oaV3mFZu/08D6erTjH/E=; t=1703180322; x=1704389922; b=KV3G+OHiqsH55cIaYskBGQlbeZE5/3hcQGdCCY75w519orXChUsHpaNwxA2ZTKTZvLtK7Ra2GfV fvyioJwHGxcobQ6c2GqO1YjJebXOkTYgVZwAqILcc87Gz8vDQzx268CP6ZK6QlbHlC5mGsquZe/dK Fa6ISylslK6sbvkFrUeQBoGDsTDQ3ynDIyGcGQT/UaVu3du5RmPa0se7LK3YAAMDbigFD7ziRFV2W wF7yOsKnpwEq3jAkUwU4P0gpaGW37EglEt4qyQBRcTiAo6Kmq249Hcl4WwVpHxtHHiiKrGXO3memE bLd8t6oH+8Vwhui0pttALNB545JH6qMs0fvA==; Original-Received: from 99-112-125-163.lightspeed.cicril.sbcglobal.net ([99.112.125.163]:39162 helo=floss) by sanpietro.red-bean.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rGN0K-0074Sl-9Y; Thu, 21 Dec 2023 17:38:40 +0000 In-Reply-To: <83a5q4gjaa.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Dec 2023 08:29:49 +0200") Received-SPF: pass client-ip=45.79.25.59; envelope-from=kfogel@red-bean.com; helo=sanpietro.red-bean.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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:314046 Archived-At: On 21 Dec 2023, Eli Zaretskii wrote: >Once again, the nsm prompt is AFAIU intentionally programmed to >work >like it does, for more than one reason. I don't think it's TRT >to >change the way we call read-multiple-choice in this case, since >the >nsm prompt could appear several time during fetching a URL, and >being >able to press a single key is a huge bonus. We would keep the ability to press a single key and have it respond instantly -- obviously that's an important part of the current user experience. I was merely proposing that `C-x o' also work, so that the user has a familiar way to break temporarily out of the "next keypress is responded to instantly" mode and go do something in the window that is currently displaying the information on which the rmc prompt's question is based. (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.) Making `C-x o' work does not imply breaking any of the current rmc behavior, unless there's something that I'm missing. Best regards, -Karl