Re: [PATCH] blame: allow -L n,m to have an m bigger than the file's line count

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jay Soffian <jaysoffian@xxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]