From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: vmalloc@gmail.com, Glenn Morris <rgm@gnu.org>,
Eli Zaretskii <eliz@gnu.org>,
16577@debbugs.gnu.org
Subject: bug#16577: Add regexp-based version of completion-ignored-extensions
Date: Sun, 20 Feb 2022 10:06:58 -0500 [thread overview]
Message-ID: <jwvley5shsv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87r17xsm7c.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Feb 2022 14:26:47 +0100")
> I think perhaps of introducing a regexp-based extra mechanism here that
> we should introduce a new completion-ignored-files variable, which would
> default to '(".svn/" ".hg/" ".git/" ".bzr/" "CVS/" "_darcs/" "_MTN/")
> (probably), and then remove those from -extensions.
BTW, maybe we can merge the two propositions:
Allow the use in `completion-ignored-files` of entries of the form
"/<RE>" where <RE> will be matched against the nondirectory part of the
file name. We'd probably want to make this match anchored, since that's
what the "/" suggests. It means that instead of "/.git/" we'd add
"/\\.git/" or "/\\.git/?\\'".
This should make the change much less invasive, with most existing uses
of `completion-ignored-files` unaffected.
Stefan
next prev parent reply other threads:[~2022-02-20 15:06 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 [this message]
2022-02-20 22:05 ` bug#16577: [External] : " Drew Adams
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=jwvley5shsv.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=16577@debbugs.gnu.org \
--cc=eliz@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).