> Is it intentional that the path to the ctags executable in both
> the exuberant-ctags parser, as well as the script pygments_parser.py
> is fixed at build time? That seems like a limitation to me.
> If someone insists on using a specific executable without touching
> the PATH variable, I guess a command line option or a configuration
> switch might be preferable.
You are right.
In fact, I have added new variable 'ctagscom' to gtags.conf file
in the master repository. Using it, you can overwrite the path of ctags
at the time of execution.
exuberant-ctags|plugin-example|setting to use Exuberant Ctags plug-in parser:\
:ctagscom=/usr/local/bin/ctags:\ <== ADDED
The next release of GLOBAL should include the facility.