From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Why does `read-multiple-choice' lock user into minbuffer? Date: Mon, 22 Jun 2020 01:37:32 +0300 Organization: LINKOV.NET Message-ID: <87366ojb9v.fsf@mail.linkov.net> References: <87r1ubfyq5.fsf@red-bean.com> <87o8pffqm2.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="74789"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Karl Fogel , Emacs Development To: =?iso-8859-1?Q?K=E9vin?= Le Gouguec Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jun 22 01:20:08 2020 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 1jn9Fw-000JJa-7r for ged-emacs-devel@m.gmane-mx.org; Mon, 22 Jun 2020 01:20:08 +0200 Original-Received: from localhost ([::1]:35924 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jn9Fv-0007bs-6u for ged-emacs-devel@m.gmane-mx.org; Sun, 21 Jun 2020 19:20:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55868) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jn9F4-0006ji-Fa for emacs-devel@gnu.org; Sun, 21 Jun 2020 19:19:14 -0400 Original-Received: from relay11.mail.gandi.net ([217.70.178.231]:49217) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jn9F2-0006bo-Ax for emacs-devel@gnu.org; Sun, 21 Jun 2020 19:19:14 -0400 Original-Received: from mail.gandi.net (m91-129-108-6.cust.tele2.ee [91.129.108.6]) (Authenticated sender: juri@linkov.net) by relay11.mail.gandi.net (Postfix) with ESMTPSA id DDD61100005; Sun, 21 Jun 2020 23:19:07 +0000 (UTC) In-Reply-To: <87o8pffqm2.fsf@gmail.com> (=?iso-8859-1?Q?=22K=E9vin?= Le Gouguec"'s message of "Fri, 19 Jun 2020 09:43:01 +0200") Received-SPF: pass client-ip=217.70.178.231; envelope-from=juri@linkov.net; helo=relay11.mail.gandi.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/21 19:19:10 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:252500 Archived-At: >> But I'd like to understand the more general question too: why does >> `read-multiple-choice' lock the user into the minbuffer so strictly? > > IIUC (but maybe I'm wrong; I'm not entirely sure I understand all the > nuances between the minibuffer and the echo-area), it's "just" an > implementation detail: read-multiple-choice uses read-event, which does > not use the minibuffer. > > So you're not actually "locked into the minibuffer" (if you were, keys > such as C-x o would be available to you), it's just that > read-multiple-choice traps you in a while-loop, calling read-event until > you hit one of the keys you are prompted for. > > FWIW, back in December[1] Juri mentioned that read-multiple-choice > should probably be patched to use the minibuffer. > > [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35564#184 Indeed, read-multiple-choice should use the minibuffer. Other similar functions were already patched to use the minibuffer.