Read the email carefully again I realized that you want to add a new option language_glob, not that telling me to use it. I misunderstood it.
Thanks you very much. I would appreciate if you implement such feature. Thanks. On Mon, Oct 13, 2014 at 6:44 AM, Shigio YAMAGUCHI <[email protected]> wrote: > Hi, > > Sorry about this. I totally forgot this email. > > No problem. > > > Could you tell me how to use the langmap configuraiton variable? > > I tried to search in GNU Global manual but it does not show > > how to write and use a configuration ffile for GNU Global. > > > > Thanks. > > Would you please ask in the help mailing list? > > Thank you in advance. > > > 2014-10-12 17:06 GMT+09:00 Tu Do <[email protected]>: > >> Hi, >> >> Sorry about this. I totally forgot this email. Could you tell me how to >> use the langmap configuraiton variable? I tried to search in GNU Global >> manual but it does not show how to write and use a configuration ffile for >> GNU Global. >> >> Thanks. >> >> On Thu, Sep 25, 2014 at 3:08 PM, Shigio YAMAGUCHI <[email protected]> wrote: >> >>> Hi, >>> How about adding new configuration variable 'langmap_glob'? >>> This variable has almost same syntax as 'skip' variable. >>> >>> For example, >>> >>> :langmap=cpp\:.c++.cc.hh:\ >>> >>> is re-writable as follows. >>> >>> :langmap_glob=cpp\:*.c++,*.cc,*.hh:\ >>> >>> If the pattern begin with '/', it is a path name from the >>> current directory. Additionally, if the pattern ends with >>> '/', it is assumed as a directory, and every file under it >>> is treated as a C++ source file. >>> >>> For example, if you want to treat every file under 'c++/4.8' >>> as a C++ source file, then >>> >>> :langmap_glob=cpp\:/c++/4.8/:\ >>> >>> $ cd /usr/include >>> $ gtags >>> >>> What do you think? >>> >>> Shigio >>> >>> >>> 2014-09-25 14:15 GMT+09:00 Tu Do <[email protected]>: >>> >>>> Hi, >>>> >>>> In /usr/include/c++/4.8/ is standard header files for C++ like >>>> iostream, string, map, set... The problem is, none of the headers has an >>>> extension, and Global just ignores them. It seems like currently GNU Global >>>> has the only options to specify a file that contains a list of files to be >>>> parsed. But then, we have to manually specify which file to include, which >>>> is tedious. For example, I want to generate GTAGS database for >>>> /usr/include, and it contains /usr/include/c++/4.8/; I have no choice but >>>> to list all files under /usr/include and save all the file paths into a >>>> file then feed it to Global via -f option. >>>> >>>> Ideally, we should be able to force Global to parse everything under >>>> specified directories. >>>> >>>> Thanks. >>>> >>>> _______________________________________________ >>>> Bug-global mailing list >>>> [email protected] >>>> https://lists.gnu.org/mailman/listinfo/bug-global >>>> >>>> >>> >>> >>> -- >>> Shigio YAMAGUCHI <[email protected]> >>> PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3 >>> >> >> > > > -- > Shigio YAMAGUCHI <[email protected]> > PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3 >
_______________________________________________ Bug-global mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-global
