> I don't think 'ctagsopt' is necessary. I prefer 'ctagsoptfile' instead > because it is simple and it keeps a clear boundary between Ctags and Global. > The complexity of 'ctagsopt' does not match the usefulness of it. > The reason why I suggested 'ctagsopt' is because I didn't understand > 'ctags-gtags.conf' is a ctags's configuration file.
'ctagsoptfile' is indeed simpler. 'ctagsopt' is currently complicated because of the proposed low-level implementation, but could be made quite simple with the proper abstractions (in passing, the argument preparation code, currently duplicated for both Windows and UNIX, should be merged and common, with the exception of small specific functions). So I personally wouldn't reject it only on the ground of its current complexity. But, personally again, 'ctagsoptfile' is enough for me also. > I have two questions: > Q1. Your patch seems to fix the bug. But if the configuration file specified > by 'ctagsoptfile' contains inconvenient options, will that bug occur again? Yes, in this case the bug will occur again. 'ctagsoptfile' opens up the possibility to have a different set of options for manual uses of Universal Ctags and other set(s) specifically for gtags. So it is useful on its own, even if for the original problem it is indeed a workaround. I don't know exactly which options of Universal Ctags are troublesome in the sense that they modify the format established through the "--_xformat" option (might even be a bug of Universal Ctags). > Q2. It seems that patched Universal Ctags plug-in parser does not load > any ctags configuration files automatically. It means an incompatible > change. Is it right? Yes. Regards. -- Olivier Certner
