From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: "vmalloc@gmail.com" <vmalloc@gmail.com>,
Glenn Morris <rgm@gnu.org>,
"16577@debbugs.gnu.org" <16577@debbugs.gnu.org>
Subject: bug#16577: [External] : bug#16577: Add regexp-based version of completion-ignored-extensions
Date: Sun, 20 Feb 2022 22:05:45 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488DDF551006CF163BB96FEF3399@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <jwvley5shsv.fsf-monnier+emacs@gnu.org>
> This should make the change much less invasive, with most existing uses
> of `completion-ignored-files` unaffected.
Most existing uses where?
If you change the meaning/behavior of
`completion-ignored-files' you'll undoubtedly
break existing code somewhere. Till now, the
extensions have been literal extensions.
If something else is needed to handle directory
names (and not even the extensions of dir names
that have extensions), then add/invent that.
Why change the use/meaning of
`completion-ignored-extensions?
next prev parent reply other threads:[~2022-02-20 22:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 11:15 bug#16577: 24.3; Ido omitting directories with similar names to other directories Rotem Yaari
2014-01-28 16:00 ` Eli Zaretskii
2014-01-28 17:18 ` Glenn Morris
2014-01-28 17:24 ` Eli Zaretskii
2014-01-28 17:35 ` Rotem Yaari
2014-01-28 17:39 ` Eli Zaretskii
2014-01-28 18:59 ` Glenn Morris
2014-01-28 19:17 ` Eli Zaretskii
2014-01-28 20:15 ` Glenn Morris
2014-01-28 21:39 ` Stefan Monnier
2014-01-29 2:43 ` Glenn Morris
2022-02-20 13:26 ` bug#16577: Add regexp-based version of completion-ignored-extensions Lars Ingebrigtsen
2022-02-20 15:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-20 22:05 ` Drew Adams [this message]
2022-02-21 14:00 ` Lars Ingebrigtsen
2022-02-21 16:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 16:20 ` Lars Ingebrigtsen
2022-02-21 16:23 ` Lars Ingebrigtsen
2022-02-21 16:57 ` Eli Zaretskii
2022-02-21 17:01 ` Lars Ingebrigtsen
2022-02-21 17:13 ` Eli Zaretskii
2022-02-21 17:36 ` Lars Ingebrigtsen
2022-02-21 17:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-21 17:33 ` bug#16577: [External] : " Drew Adams
2022-02-22 13:17 ` Lars Ingebrigtsen
2022-02-22 13:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-23 12:05 ` Lars Ingebrigtsen
2022-02-20 21:48 ` bug#16577: [External] : " Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488DDF551006CF163BB96FEF3399@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=16577@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
--cc=vmalloc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).