GNU bug report logs - #16577
Add regexp-based version of completion-ignored-extensions

Previous Next

Full log

Message #62 received at 16577 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: vmalloc <at> gmail.com, Glenn Morris <rgm <at> gnu.org>, Eli Zaretskii <eliz <at> gnu.org>,
 16577 <at> debbugs.gnu.org
Subject: Re: bug#16577: Add regexp-based version of
 completion-ignored-extensions
Date: Mon, 21 Feb 2022 17:20:54 +0100

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>> I haven't looked at the various code snippets that use the resulting
>> regexps, but I imagine that some are matching on the full file name and
>> some aren't?
>
> I think the important case only has the nondirectory part of the file
> name at hand, which is why I propose for "/<RE>" to be defined as
> matching only on that part (with a terminating / if it's a directory).

Oh, so this wouldn't be a plain regexp, but a ... mini-language where
"/" has a special meaning?  I think that sounds pretty confusing.

> No, the "/" would look like it's matching the / of a full file name, but
> it would really be just a marker to indicate that the rest is a regexp
> (and where it's anchored) and the matching code would extract the regexp
> from it (and replace it with the equivalent of \\(?:\\`\\|/\\) as
> needed).

Hm.  I think it'd a more straightforward interface to just keep regexps
out of it all, but I see the attraction of having a regexp interface,
too.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.