I see that option reading and initializing was removed from tagmanager/ctags/options.c:
#define readOptionConfiguration #define initOptions #define freeOptionResources
I assume there are good reasons for this, but would it be too difficult to make the embedded ctags read ~/.ctags? Would it take a lot more effort than more or less copy&pasting some code from the official ctags?
I understand one can just write a C extension for ctags, even one only relying on regexs the same as would be done in ~/.ctags, which is not that hard, but it would be nice to avoid geany recompilation for simple tasks.
Any advice will be very much appreciated.
On Mon, Nov 18, 2013 at 11:25 AM, Carlos Pita carlosjosepita@gmail.com wrote:
I don't think so, but I'm not 100% positive. I'm sure Geany won't recognize a new language added like this, but I'm not 100% sure you
Can anyone else confirm this? IMO this is an important point from the extensibility perspective. If a language is not supported out of the box you need to be able to configure both geany workhorses: scintilla and, in this case, ctags.
Or maybe ctags configuration could be done at the geany language level (filetypes.*) instead of at the system user level (~/.ctags). That seems the correct way to do it but also looks harder to implement. I don't know how difficult it is to initialize the embedded ctags with specific options or to instruct it to load some initialization file at startup.