Actually it doesn't make much different if the new plugin would compile or lint the code from a technical point of view because linting as well as compiling in Geany is just executing a configured command and parse its output.

I also want such a plugin (for linting) but didn't manage to find the time to start writing it.

For any volunteers: in a basic variant it might be easy:
take Save Actions' Autosave feature, put it into a new plugin and run the configured "Compile" or "Build" command for the current file (the configured build commands are different per filetype).
I'm not sure if the configured build commands can be read via the plugin API, if not, such an API could be added.

In a more comfortable variant (maybe after the first basic version is working), one could ideally configure which of the available build commands is executed per filetype.

Still I would suggest to use Geany's Build commands at all for this feature as for these we already have good support in parsing and showing the output (in the Compiler tab at the bottom) and they are well tested and work fine.
Implementing all this again in the plugin would be quite overkill.

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