> we write: > > :gtags_parser=user-custom: > :gtags_parser=exuberant-ctags:
How to know the library directory and suffix? > Leave the job to `global', `gtags' and whatnot to figure out where to > find it. What do you think? There is no problem if the contents of the job is clear. However, it seems that it requires a set of hard coded rule for path specification instead of real path name. Isn't it unclear for the users on the contrary? Shigio 2014-10-05 9:29 GMT+09:00 Leo Liu <[email protected]>: > On 2014-10-04 17:56 +0900, Shigio YAMAGUCHI wrote: > > Surely hard coded path names are hard to use it. > > How about enabling use of shell style variables > > in the configuration file? > > > > * Variable 'libdir' has a default value. > > > > :gtags_parser=C\:$libdir/gtags/exuberant-ctags.la:\ > > > > * You can change the default value freely. > > > > :libdir=/tmp/var/lib:\ > > :gtags_parser=C\:$libdir/gtags/exuberant-ctags.la:\ > > > > * Of course, the followings usage is acceptable. > > > > :ctagslib=$libdir/gtags/exuberant-ctags.la:\ > > :gtags_parser=C\:$ctagslib:\ > > > > * Syntax ${...} is also acceptable. > > > > Any comment? > > It seems this would make it easier to change the value of the plugin > path by consolidating them in one place. i.e. it is an improvement. > > I wonder if it can be made even better without leaking the plugin path > to user's configuration file (.globalrc). So instead of > > :gtags_parser=c\:/usr/local/unix/global/lib/gtags/user-custom.la: > :gtags_parser=Asm\:/usr/local/unix/global/lib/gtags/exuberant-ctags.la: > > we write: > > :gtags_parser=user-custom: > :gtags_parser=exuberant-ctags: > > Leave the job to `global', `gtags' and whatnot to figure out where to > find it. What do you think? > > Thanks, > Leo > > > _______________________________________________ > 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
_______________________________________________ Bug-global mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-global
