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: Sun, 14 Jul 2024 12:16:53 +0000 Message-ID: <87frscjhhm.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> <87zfqlpfty.fsf@localhost> <86jzhpjt4x.fsf@gnu.org> <87r0bxpecj.fsf@localhost> <86ikx9jrh4.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="31354"; 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 Sun Jul 14 14:16:37 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 1sSy9c-0007wd-Kp for ged-emacs-devel@m.gmane-mx.org; Sun, 14 Jul 2024 14:16:36 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sSy8l-0006UO-Vf; Sun, 14 Jul 2024 08:15:44 -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 1sSy8f-0006TP-7t for emacs-devel@gnu.org; Sun, 14 Jul 2024 08:15:37 -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 1sSy8T-0006eg-Rn for emacs-devel@gnu.org; Sun, 14 Jul 2024 08:15:36 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id C3ACD240027 for ; Sun, 14 Jul 2024 14:15:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1720959321; bh=ZHuY9oL02VrMUHEHYXbSuQcXGy7uNFJmpoau+HKX7PI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=VwY2IpTmqTXZYaa0iwMl4/N5FqB1dlGQFwgFwaBNqg+OPKH2mflunonuzJ53KI/G+ t+/48iuTj9lQoT/Cb2UaGDBRWr8BX3/8m+YxX++xEXmWISr/VoqEtCAtjBnzjzQmc4 h7mCcfOhu/rFx84ZW5//6EjvhBvt8ZBUjI9xY/N6blhWUrAWtzLzsDW6+PUzyuuzU4 /xHInd/vlu9RG/FCTuGL+gsLoRrfMvPl7jOrEdoIJsR1CtGxgOE6SsosoJY+YOOL4J 3iSEAOTBFCCsEenSVFnNaAFSB9x4WRiFvmLk0veFS4mwkBa0/IJj1Sii+V+M7P8F3E 91hBFMEQsOhAg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WMPRY1FLgz6tyB; Sun, 14 Jul 2024 14:15:20 +0200 (CEST) In-Reply-To: <86ikx9jrh4.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.01, RCVD_IN_MSPIKE_WL=-0.01, 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:321638 Archived-At: Eli Zaretskii writes: > Why do you need the minibuffer part "Choose files: CO"? why not simply > let users mark the selected files using Dired mark commands? > ... > How did "completion" enter the picture? The original question was > about ways to select multiple files, which is much wider and more > general than just completing on file names. When the user needs to > select a file, completion is just a means of saving them some typing. > That idea basically becomes irrelevant when users need to select > several files whose names might not have anything in common. GUI > applications have solved this problem long ago, so why should Emacs > insist on inventing its own idiosyncratic solution? In my use case, the user may not immediately know if she needs to attach a single file or multiple files. So, having two separate interfaces for single file vs. multiple files is awkward. Moreover, in my experience using a similar command (implemented using helm), completion is actually extremely useful: 1. It is much faster to jump to specific folder using completion vs. using in-buffer navigation in dired. Especially when I am looking for deeply nested folders. 2. It is not uncommon for me to attach files that have common names. Having completion under the fingertips is better compared to manually entering dired filters. (in dired, there is an extra key sequence required) I can totally see some people preferring dired buffer UI to select files, but then I do not see why the same people would not then prefer dired to select a single file as well. Is it something you think would be worth having (dired as _single_ file selection dialogue)? -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at