[Github-comments] [geany/geany-plugins] geanyprj/workingdir (#486)

[Donjan Rodic]

@elextr I'm aware that it shouldn't be needed, it was just one attempt on the way of achieving point 1. So, understood: no usage due to not being in the documented API :)
Probably fixing `build_remove_menu_item()` should be handled in a separate bug report.

Side note: the changes presented here work nicely when switching between geanyprj projects and also when loading a Geany core project file.
My issue is that when tabbing from a geanyprj file to a non-project file, the build menu needs to be repopulated as given by the file type and `geany.conf`.

I can't play with the current `GeanyBuildSource` values because chosing below `GEANY_BCS_HOME_FT` is not enough to make geanyprj settings show up, while using `GEANY_BCS_HOME_FT` or `GEANY_BCS_PREF` lets the project paths linger (not get updated) at non-project files due to same priority in the respective cases.

One solution would be a plugin API that lets me reload stored settings from the config files (which I don't see currently).

Another one would be to introduce something like `GEANY_BCS_PLUGIN` either higher than or just below the `GEANY_BCS_PROJ` entries, so plugins get their own place for build menu changes.

Thoughts?

-- 
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-plugins/pull/486#issuecomment-258687870
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20161106/ed614a6a/attachment.html>