Plugins can currently only change build commands by changing a user or project setting. This requires the plugin to read the existing setting (or its absence) and to save that and restore it in a timely manner before Geany saves the project or user config, or when the plugin is disabled, otherwise the plugin settings will get saved to the config/project files overwriting user settings.

This proposal is to provide another build command source exclusively for plugin use that is not saved by Geany. For that to work it would need to be highest priority, and thats reasonable, the user has enabled the plugin to do its thing and presumably understands that it will set build commands.

This would also allow the plugin to modify build commands as the current tab changes, effectively providing per-file settings. This would support project plugins that want to apply their settings only to the documents that they perceive as part of the project and for plugins which need to manage build options to support language libraries like libclang that need full build control and need to make Geany build commands match. There have been discussions relating to both of these use-cases.

Discuss.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.