Re: [RFC] The design of new pathspec features
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Jan 29, 2013, 05:27 UTC
- Message-ID
- <CACsJy8BPhHJseDghWjCe1xK_KqSZOz1cfoOfPnTdex94qqrCzw@mail.gmail.com>
- In-Reply-To
- <7vpq0otw7y.fsf@alter.siamese.dyndns.org>
On Tue, Jan 29, 2013 at 12:05 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
>> New way to specify long pathspec magic
>> ======================================
>>
>> While testing the pathspec magic code, I grow tired of quoting :(glob)
>> every time because '(' is the start of a new shell. Which is one of
>> the reasons I introduce --[no]glob-pathspecs. Still I'd like a way to
>> specify long pathspec magic without quoting.
>
> Is this a real issue, though? Often interesting pathspecs do have
> shell globs in them and we have to quote them anyway.:(icase) often won't (unless you combine with :(glob)). If we turn grep's --max-depth feature into pathspec magic (feasible, just not sure if it's actually useful), it won't need quoting either.
Even with :(glob), because of the complexity of the pathspec, it's less likely to match anything and be expanded by bash, so no quoting required.
>> How about making ":q/xxx/" an equivalence of ":(xxx)"? > > A moderately strong no from here.
-- Duy