Re: Ctags path fixed at build time
Shigio YAMAGUCHI <[email protected]>
| Newsgroups | gmane.comp.gnu.global.bugs |
|---|---|
| Message-ID | <CADJmJYotJqv0fGCGB5mYeAr9HO=7dJ22vfy+ZQu+rPQOWCq5aw@mail.gmail.com> |
Hi,
> 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.
[gtags.conf]
exuberant-ctags|plugin-example|setting to use Exuberant Ctags plug-in
parser:\
:tc=common:\
:ctagscom=/usr/local/bin/ctags:\ <== ADDED
:ctagslib=$libdir/gtags/exuberant-ctags.la:\
...
The next release of GLOBAL should include the facility.
Regards,
Shigio
--
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