One more vote for seeing uses of this. I'm a little worried about adding more API before anyone actually uses it (especially API like this which is just a facade for what is already accessible). I understand the performance problem but the question is how many people will want to create python plugins working with TM; in geany-plugins there are just geanygendoc, projectorganizer and geanyprj dealing with TM and it doesn't seem someone would want to create TM-using plugins very often.
> Another goal is to eventually use this in the existing tag search/query > functions. For C this new API is more or less useless because the filtering can easily be done by directly looking at the tag values and IMO it's more explicit and clearer than using some layer in between. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/1187#issuecomment-241649575
