[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-10-10 Thread Jiří Techet via Github-comments
> Closing now https://github.com/geany/geany/pull/3547 has been merged. Feel > free to open further adjustments again  As a last minute patch just before the release :-). -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3542#issuecomment-1755318284 You

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-10-10 Thread Colomban Wendling via Github-comments
Closing now #3547 has been merged. Feel free to open further adjustments again :wink: -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3542#issuecomment-1755254335 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-10-10 Thread Colomban Wendling via Github-comments
Closed #3542. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3542#event-10603526637 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-22 Thread Jiří Techet via Github-comments
> What about a hybrid where if there's no parameter list and no scope info then > show file and line. Nobody will understand that. For users it will just confusing why they sometimes see filenames and sometimes the signature. And as for me (and apparently @kugel- and @elextr too), always

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-22 Thread Nick Treleaven via Github-comments
BTW this pull only adds info to the menu so I'd like to merge it. Though maybe you want the configuration option before going ahead with refining the pull that shows signatures. -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-22 Thread Nick Treleaven via Github-comments
I can make it configurable. @techee how are you getting those text declarations? It seems like there should be some scope info probably. What about a hybrid where if there's no parameter list and no scope info then show file and line. -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-21 Thread Thomas Martitz via Github-comments
The file is absolutely necessary information for me. I typically edit multiple checkouts of the same code (managing different features/bugs/tasks simultaneously, so I can work on one thing while waiting on review for the others things). Often this involves the same files. So I quickly need to

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-21 Thread elextr via Github-comments
@eht16 the windows CI appears to be broke again. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3542#issuecomment-1687265550 You are receiving this because you are subscribed to this thread. Message ID:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-21 Thread elextr via Github-comments
What one IDE does that seems to work for autocomplete (its goto is precise AFAICT so no list needed for that) is to display the list of unique names only and then for the selected one a fixed width multiline subwindow shows one of the the overloads with full file, line, and signature and an

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-21 Thread Jiří Techet via Github-comments
I'm still not very happy with the result: https://github.com/geany/geany/assets/713965/ec1fa8fa-55ac-4e3c-a087-bfda3a8eba61;> I understand that seeing the signature may be useful in some cases (like multiple constructors) but it doesn't answer the question *where* will the jump go which is

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-14 Thread Nick Treleaven via Github-comments
@ntrel pushed 1 commit. c3aae8a62d787727b7421bbb81445b99e9f56412 Show scope with tm_parser_format_variable -- View it on GitHub: https://github.com/geany/geany/pull/3542/files/73ba78da1c114c2da0e10abcea2caa7e6db3cba3..c3aae8a62d787727b7421bbb81445b99e9f56412 You are receiving this because you

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-14 Thread Nick Treleaven via Github-comments
@techee The list of variables would be much more useful if it showed the scope, e.g.: ![image](https://github.com/geany/geany/assets/1107820/aa3a95da-c674-4aa9-bfd6-54518d4d9cd4) I'll add that. -- Reply to this email directly or view it on GitHub:

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-13 Thread Jiří Techet via Github-comments
Also, regarding the ellipsize, I think it would be useful to split it into two parts: 1. path plus line number - max length 40 with `PANGO_ELLIPSIZE_START` 2. signature - max length 40 with `PANGO_ELLIPSIZE_END` and then join them for the resulting string. This way you'll always have the file

[Github-comments] Re: [geany/geany] Improve Go to Tag menu (PR #3542)

2023-08-13 Thread Jiří Techet via Github-comments
I don't know but wouldn't it be better to do it the other way round - i.e. display the file name and line number directly in the list as before and show the signature as a tooltip? What I get right now doesn't seem very useful and if you for instance want to navigate to gpointer data, one would