.@gmail.com [mailto:i.tama...@gmail.com] On Behalf Of
> > Shigio YAMAGUCHI
> > Sent: 04 October 2016 01:19
> > To: Cooper, Anthony
> > Cc: bug-global@gnu.org
> > Subject: Re: GNU Global Parsing Suffixless Files Patch
> >
> > Good morning :)
> > I unders
s about
> the specification not about the implementation.
>
> Regards,
> Shigio
>
>
> 2016-10-03 21:34 GMT+09:00 Cooper, Anthony
> <anthony.coo...@gchq.gsi.gov.uk>:
>
>
> SECURITY CLASSIFICATION: OFFICIAL
>
>
> Good morning :-) (See comments be
higio YAMAGUCHI
> > Sent: 01 October 2016 00:17
> > To: Cooper, Anthony
> > Cc: bug-global@gnu.org
> > Subject: Re: GNU Global Parsing Suffixless Files Patch
> >
> > Before implementation, I would like to make clear the specification.
> >
> > > Assorted p
Before implementation, I would like to make clear the specification.
> Assorted projects I've come across have include and Include (the example
below is
> a trivial but a real one relating to MS-Windows) and some even have
include dirs
> names XInclude or something similar (can't remember the
@gnu.org
Subject: Re: GNU Global Parsing Suffixless Files Patch
> I still feel the regex approach offers more flexibility. How about we
> adopt the () approach you mentioned below such that:
>
>gtags --language-force=cpp\:project/include
>
>Is a real p
> I still feel the regex approach offers more flexibility. How about we
adopt
> the () approach you mentioned below such that:
>
>gtags --language-force=cpp\:project/include
>
>Is a real path as you suggest and:
>
>gtags --language-force=cpp\:([Ii]nclude)
Tony.
-Original Message-
From: i.tama...@gmail.com [mailto:i.tama...@gmail.com] On Behalf Of
Shigio YAMAGUCHI
Sent: 28 September 2016 02:51
To: Cooper, Anthony
Cc: bug-global@gnu.org
Subject: Re: GNU Global Parsing Suffixless Files
