New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commander does not show filetype-specific build commands #462
Comments
This seems to happen because, when populating the Build menu, Geany sets text directly on the
that seems to fix the issue. @elextr Could you comment on why you implemented it like that? |
@vfaronov as the comment mentions, That little wrapper function can probably be dropped by now and just set the labels normally. |
As @codebrainz said. |
The API exports functions to access the build commands, including the labels. @b4n the commander plugin should be using that, not scraping the widgets. |
Wow, you earned like 10k credits points for finding this out in what looked like a timely manner 👍
Well, one of the purpose of the Commander plugin is to be able to trigger any menu item generically, without duplicating every feature (or at least knowing about it and labeling it). So I'd rather not special case the build commands if it can be avoided. |
GTK+ 2.16 is seven years old. Would it be reasonable to bump Geany’s GTK+ requirement to >= 2.16 and replace |
I have configured some build commands for my project:
In Commander, I can invoke independent commands (such as “Run tests”) and execute commands (such as “Run on test input”), but not filetype-specific commands (such as “Pylint”). It seems like Commander just doesn’t see their labels:
The text was updated successfully, but these errors were encountered: