Eric Blake wrote:
> On 01/27/2011 08:16 AM, Jim Meyering wrote:
> @grep -nEA2 '[^rp]error *\(' $$($(VC_LIST_EXCEPT)) \
>>>
>>> Is there a way to tighten it, by passing the grep output through a sed
>>> script that combines multiple lines (easily determined by the difference
>>>
On 01/27/2011 08:16 AM, Jim Meyering wrote:
@grep -nEA2 '[^rp]error *\(' $$($(VC_LIST_EXCEPT)) \
>>
>> Is there a way to tighten it, by passing the grep output through a sed
>> script that combines multiple lines (easily determined by the difference
>> between file: and file- f
Eric Blake wrote:
> On 01/27/2011 07:47 AM, Jim Meyering wrote:
>> Simon Josefsson wrote:
>>> Is the regexp wrong here? It looks fine to me, maint.mk:
>>>
>>> # Error messages should not start with a capital letter
>>> sc_error_message_uppercase:
>>> @grep -nEA2 '[^rp]error *\(' $$($(VC_LIST_
On 01/27/2011 07:47 AM, Jim Meyering wrote:
> Simon Josefsson wrote:
>> Is the regexp wrong here? It looks fine to me, maint.mk:
>>
>> # Error messages should not start with a capital letter
>> sc_error_message_uppercase:
>> @grep -nEA2 '[^rp]error *\(' $$($(VC_LIST_EXCEPT)) \
T
Simon Josefsson wrote:
> I got this from 'make syntax-check' in a project:
>
> oathtool/oathtool.c-225- printf ("Step size (seconds): %ld\n",
> time_step_size);
> oathtool/oathtool.c-235-printf ("Time now: %s (%ld)\n", outstr, when);
> maint.mk: found capitalized error message
> make: ***
