@LarsGit223 I havn't had a chance to look at this in detail, but is it only per-filetype, or do you have a set that is filetype independent? Or are filetype independent context actions still limited to one puny no pattern command?
AFAIK nothing in the filetype files has a GUI, so its probably ok to leave those without (well except for `Tools->Configuration Files->etc etc` editing). The filetype independent probably needs a GUI since its tricky to edit `geany.conf` since Geany re-writes it all the time, but agree that GUIs for variable numbers of things is more complex since it has to be generated by code not Glade, see the `Set Build Commands` dialog. And maybe independent ones should be stored/read from the project file if its open, and project filetype ones ... getting flashbacks of creating the build command system ... so maybe this can be another follow on pull request. :grin: -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/1643#issuecomment-343611948
