From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 12 Feb 2010 00:25:24 GMT
Subject: Re: [PATCH] blame: allow -L n,m to have an m bigger than the file's line count
Message-ID: <7vfx57mhaj.fsf@alter.siamese.dyndns.org>
In-Reply-To: <76718491002101139m4061fb90qcee7d34fca9f242f@mail.gmail.com>

Jay Soffian <jaysoffian@gmail.com> writes:

>> Another thing we _might_ want to consider doing is something like:
>>
>>    -L'*/^#ifdef WINDOWS/,/^#endif \/\* WINDOWS \/\*/'
>>
>> to tell it "I don't care to count how many WINDOWS ifdef blocks there are;
>> grab all of them".
>
> That was my aim, but the syntax I'd settled on was to use
> -L/pattern/..END where END is either a numerical argument or another
> pattern. IOW, ".." instead of ",".

I would suggest against using that syntax.

Users of different systems use A,B or A..B as range notations, but there
isn't anything that helps the unsuspecting learners to learn and memorize
that double-dot variant A..B has a repeating semantics and comma A,B does
not.