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
Feature: Custom command menu items #2764
Comments
You know you can extend the build commands menu? https://wiki.geany.org/howtos/configurebuildmenu |
@elextr Nice, but not sure if "Build" is the right menu for this task, the GUI is also limited in the way how it only provides a fixed number of additions. |
No its not, read the fine wiki article! |
Actually the menu size settings are now in various I think, don't forget to restart Geany though. |
@elextr I have glanced the wiki and I am aware that it is possible to add additional options by directly editing the configuration files, but the GUI itself doesn't allow more than 4 independent commands... but I see the complexity with integrating my proposed feature with the existing build commands feature. |
As I said above, you can set the number of each type of command with I just set non_ft to 12, restarted and then |
Hmmm, how useful, anyway if build and custom are not suitable "somebody" can indeed make a plugin as you said, |
Hi, I just thought about this feature though I am sure many others might have come up with the same idea, I could not find a related ticket here so I am posting it for the first time (forgive me if I missed the duplicate).
The basic concept is that there will be a new section in the menu for custom labelled commands, which will execute user-defined commands, with the option of having some wildcard options to replace with the current file's path or parent directory, work directory etc.
I could already think of a few uses for this feature:
xdg-open %s
myterminal %w
(working directory or file's parent directory)Hopefully it is not too hard to implement, it may even be implemented as a plugin 😄
P.S I am aware that there is a "Send selection to custom command" but that really isn't the same feature.
The text was updated successfully, but these errors were encountered: