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: Q: Is there a built-in way to read multiple file names? Date: Sat, 13 Jul 2024 13:43:53 +0000 Message-ID: <87zfqlpfty.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> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2320"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mardani29@yahoo.es, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 13 15:43:18 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 1sSd1x-0000R6-UR for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Jul 2024 15:43:18 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sSd1C-0005d7-Cm; Sat, 13 Jul 2024 09:42:30 -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 1sSd1A-0005cx-DW for emacs-devel@gnu.org; Sat, 13 Jul 2024 09:42:28 -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 1sSd15-0001E0-6s for emacs-devel@gnu.org; Sat, 13 Jul 2024 09:42:28 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 5FE6A240028 for ; Sat, 13 Jul 2024 15:42:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1720878141; bh=+OX6Zr6UQzIpOVz2Px5aBMKXzczwKOiwehS19qT1Gcg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=ixKG4iC/2ZWLYt4COa1JCAMRSMwsJ/PbQWpLlimlXRcg6T2rB+pkBDcnmAmAFfGt/ REoIGI742Ss7btOIRXWn+vjurWBgyFTc57UXbgtkQh8j/+vt4w85bUFrqfGyzgWH1L 6TDcWc2GnKs6Jap47uRo05owPpqjFIGNmO7ZjMxDJ1iBv/GkqoWPkOykx+v/CpmVkh zyZttM3/A7rHrt3nuljDdoUl9RTpdyVn/mAgNauZDoAF9OSK9Sy1jEehKEqBAQeNtb EZNby6CpgnoBx3xVhmqR/KYs9041Ig5eaTKioQa7+hDEHyOF38umJyjD9n5AkN+now AB2zKGcDUzg2A== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WLqQN4RlQz6tx2; Sat, 13 Jul 2024 15:42:20 +0200 (CEST) In-Reply-To: <86ikxh13yc.fsf@gnu.org> 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_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01 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:321604 Archived-At: Eli Zaretskii writes: >> My concern about dired and similar is that it is not possible to exit >> them and go back to the original place as easily as C-g in the >> completion prompt. Interactive narrowing is also not as easy as in the >> completion. > > I didn't mean Dired as use it for browsing a directory. I meant a UI > for selecting multiple files that reuses Dired, and lets users exit it > with "C-c C-c" or somesuch. > > IOW, my intent was to point out the features to generalize and extend > in order to have what you want. (For buffers, I think Ibuffer already > offers an almost complete solution.) May you please explain in more details how you envision such multi-file selection interface? (For context, I am interested in this question to extend M-x org-attach where I want to allow users select multiple files at once; or, similarly, to extend the email attachment prompt) >> IMHO, helm proves that completion framework can be used for very quick >> selection. It does it via: >> >> 1. The notion of "current" candidate from the list that can be navigated >> right from the minibuffer (like next/previous-completion in the >> *completions*) >> 2. minibuffer command to mark/unmark candidates quickly >> 3. ability to retain marked candidates even the prompt input changes >> >> I find it quick and convenient to use, despite being a completion >> framework. >> >> I also do not see why the same cannot be done based on the basis of >> completion-list-mode. > > The display parts might be suitable for selection, but the entire > completion machinery behind this makes absolutely no sense for the > purpose of selection based on attributes that are not names or > collection of strings. Is it? AFAIK, packages like consult allow searching by metadata. Isn't custom COLLECTION function not suitable? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at