From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: RE: [External] : Re: Q: Is there a built-in way to read multiple file names? Date: Wed, 17 Jul 2024 17:21:42 +0000 Message-ID: <87r0bs53yx.fsf@localhost> References: <875xthfyz3.fsf@localhost> <87a5it6vr6.fsf@localhost> <86r0c5196r.fsf@gnu.org> <877cdx6ryu.fsf@localhost> <86o77914sh.fsf@gnu.org> <874j916qlv.fsf@localhost> <86ikxh13yc.fsf@gnu.org> <87wmlppf7e.fsf@localhost> <875xt8jgho.fsf@localhost> <87o76yiivc.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39114"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , "mardani29@yahoo.es" , "emacs-devel@gnu.org" To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 17 19:21:06 2024 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 1sU8Kv-0009zU-AQ for ged-emacs-devel@m.gmane-mx.org; Wed, 17 Jul 2024 19:21:05 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sU8KF-0000z1-U9; Wed, 17 Jul 2024 13:20:24 -0400 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 1sU8KC-0000oV-FW for emacs-devel@gnu.org; Wed, 17 Jul 2024 13:20:22 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sU8K7-00049q-O1 for emacs-devel@gnu.org; Wed, 17 Jul 2024 13:20:18 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 7AFE2240027 for ; Wed, 17 Jul 2024 19:20:12 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1721236812; bh=qSjsuZNmcwrD16hTruvePCZK3LdRAeoI/tXpfJre7P0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=kcx7GcyK4Xa/lapEJIAxdcYhJzXZzM1FOJJYkMg7EML0O5WooosNj4R1MDGKYENeu HF2uq+zvDtkKjC/laihhjiTVo4us5GO+Rm+rNwc6soVJBxzCq/LM4Kir9dYalg/sth JXju1JhaK3hO8Xk5hQsg9hDzYoxrQuCLmK1IbJLOyiyi14HqiUneL9o9hns8tiwUm1 gIadljmkdevRFUw0uVmFOaDV6oFGf7P4wLdAL4Q8XnKBMJSHGWd675v4PB0UaxutEN qgRoxZR0wpD11FdfL6YPlOZmkilf7Xmgl02FoLPkp+lfs4sO/ZzZRK0qQ+bGKjRJ6B BV4Imo1Op4xqQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WPN3w0LlTz6txx; Wed, 17 Jul 2024 19:20:11 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable 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:321760 Archived-At: Drew Adams writes: >> Sure. But if multi-selection is incorporated into standard APIs, history >> may also hold the information about selected elements, in addition to >> minibuffer input. I do not see a reason to keep it as a completely >> separate structure. > > Sorry, not clear to me. Define "history of selected > elements". > > By "selected elements" I assume you mean something > like what we've been discussing: designating/marking > some file names (or more generally any kind of > completion candidates) for use as a group at some > time, particularly at some time other than during > the current act of completing patterns. Not really. In this thread, I am not discussing multi-selection in the completing read commands that are not asking for multiple answers. What I am interested in is extension of the UI of `completing-read-multiple' - when Elisp code _asks_ for one or more inputs. I understand that icicles is doing more than this, but I am not interested in icicles as is. Just in the ideas it introduces as they might be used in the more conventional Emacs workflows (read-multiple in particular) -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at