Hi,
> Thank you for planning this feature. I think it makes the configuration
> more flexible which is a good thing. The key thing is to give it some
> sort of inheritance:
>
> project configuration > $HOME/.globalc > system-wide configuration
It is too vague for discussing. Would you please explain it for example?
In what case is it useful?
> > 1.2 gtags.label
...
>
> But we should keep the interface as simple as possible. Introducing
> another file is another complication. For example in my drupal project's
> gtags.conf I have:
>
> default:\
> :tc=native:tc=drupal:
>
> So I already have the ability to pick and compose any label. I think we
> should also get rid of the .notfunction file and move this feature to
> gtags.conf.
Since gtags.conf has a function to hold two or more configurations in
one file, a configuration is specified by both file name and label name.
If we offer project basis gtags.conf, we should also offer project basis
label, I think.
Use of gtags.label is completely upward compatible. If unnecessary for you,
you need not use it. It is completely transparent also for the systems
which use GLOBAL. So, it does not bring any new complication.
> BTW, the configuration uses TERMCAP style. Could you point me to its
> official specification?
About file format, it should be same as termcap.
About environment variables, please replace as follows, respectively.
TERMCAP -> GTAGSCONF
TERM -> GTAGSLABEL
About the individual variables, it is not fully documented.