IMO the tool is mostly at fault spamming `stderr` when all is well; proper UNIX commands are supposed to be quiet by default when all is well.
Also, Geany considering content on `stderr` means a failure is IIRC due to some tool improperly exiting with exit status 0 while having failed. So that's a workaround already, but so long seemed ok (and it's like this for a long time) -- and we probably *should* take the safest path here. The only way to fix would be to enhance the Custom Commands so you can select the behavior, but it might be out of its scope. So IMO your workaround to silence the tool is the best way to go. But exiting with `0` no matter what seem dangerous. You probably could simply use `sh -c 'yourcommand 2>/dev/null'` as the custom command. PS: don't tell anyone, but I once planned to write a plugin for enhanced custom commands-like functionality, that could allow for all this fancy options, and more. But it's not done yet. --- 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/issues/1118#issuecomment-230902940
