It's just a GtkTreeView. It could be as simple as Geany setting up the cell renderers and the model and then calling into a plugin to fill in the model.

Did you have a look at the code? It's pretty non-trivial to update it with changes only so the tree doesn't jump on update...

I don't really see why. It wouldn't be hard to traverse the AST and generate a tags list, filling in the scope with the correct path/namespaces.

...but if you are fine with feeding it with some TMTag-like array, it should be fine.

I indeed believe you should be able to feed the tags into TM. But my impression was you wanted to use only this info from TM to perform autocompletion which I think isn't sufficient.

IIUC Ctags and not TM is responsible for the broken scope support in Geany.

It's partly scope information (using namespace not taken into account) and local variables aren't parsed which limits the autocompletion functionality. In addition, there's no visibility information for symbols so it isn't clear if the symbol is available at the given place (e.g. if corresponding header containing its declaration was imported). And this is something you won't be able to store into the tags and for which you'll probably need the AST for autocompletion.

That's the idea. The language support libraries already provide their own specific TM-like APIs, no point in re-inventing that generically when most of the needed features (filling in a treeview, filling in a listview, providing a location of declaration, etc) can be accomplished more easily on the plugin side if they have access to the actual language implementation libraries.

Sounds good then.

@kugel- sorry for hijacking the comments here, we should probably move unrelated discussion to the mailing list.

Yep, sorry here too - ending now.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.