With this PR class tooltips would look like:

geany_py_calltip_custom_class_original
geany_py_calltip_custom_init
geany_py_calltip_global_tag_class

also modifying the calltip code to show the class name instead of __init__.

after this it would look like:
geany_py_calltip_custom_class

Great idea.
The other variants keep the same.
If you agree, I'd commit that change.

There is still a difference: signatures created by ctags (also within Geany) list the "self" argument as part of the signature while it is missing from the generated tags file. Adding it to the generated tags file would be easy (probably).
But this raised the question if "self" should maybe dropped from the calltip for Python at all. This is another very Python specific thing: each method must accept a first argument, called "self" by convention, but this argument is never passed when calling the method.
So, the signature should contain the special argument while a calltip probably should omit it as you must not pass it when calling the method.

On the other hand, this would require even more Python specific code :(.
What do you guys think?


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <geany/geany/pull/3334/c1321212468@github.com>