Re: [RFC] The design of new pathspec features

From: Duy Nguyen <pclouds@gmail.com>
Date: Jan 29, 2013, 12:17 UTC
Message-ID: <CACsJy8A5VJ4EchbeFEC5ikLYgHze47_xyLTtgH=kqVpP15Hogw@mail.gmail.com>
In-Reply-To: <20130129043517.GA2878@duynguyen-vnpc.dek-tpc.internal>

On Tue, Jan 29, 2013 at 11:35 AM, Duy Nguyen <pclouds@gmail.com> wrote:

Show 10 quoted lines

> :(glob) magic
> =============
>
> This magic is for people who want globbing. However, it does _not_ use
> the same matching mechanism the non-magic pathspec does today. It uses
> wildmatch(WM_PATHNAME), which basically means '*' does not match
> slashes and "**" does.
>
> Global option --glob-pathspecs is added to add :(glob) to all
> pathspec. :(literal) magic overrides this global option.

I forgot one thing. The current pathspec behavior, the pattern "[a-z]" would match a file named "[a-z]" (iow, wildcards are also considered literal characters). Do we want to keep this behavior in :(glob)? To me it's a surprise factor and therefore not good. But common sense may be different.

-- 
Duy