[Geany-devel] Killing Builds

Thomas Martitz thomas.martitz at xxxxx
Thu Aug 20 13:49:32 UTC 2009

Enrico Tröger schrieb:
> On Wed, 19 Aug 2009 10:06:20 +1000, Lex wrote:
>>>> Can it at least be auto closed, say if the script returned success
>>>> (i.e. 0)?
>>> Well we *don't* want normal executes to do that,output should be
>>> shown even if the program ran successfully, so some configuration is
>>> needed. I don't know how easy it would be to do either, it has to
>>> work for external terminals and for VTE if thats what is being used.
>>>  Oh and potentially for windows when builds are corrected to be
>>> asynchronous again.
>>> Cheers
>>> Lex
>> It looks like it could be mostly handled already, just need the
>> configuration.  Do *not* want to make the build menu configuration
>> dialog bigger (do we Enrico :-) so some other option needs to be used.
>> I won't do this until after build-system is in trunk.
> It seems you know me already pretty good :)
> No, I do not want to have more options and more special commands for
> Thomas' need to kill builds (btw, Lex' joke about film titles was
> coool). Don't get me wrong but I don't see this as that important,
> usually (!) you want a build to finish and not kill it for whatever
> reason. And if so, opening a terminal and type 'killall make' isn't
> that hard, I guess.

As we've established in the other thread, killall make isn't an option, 
since it kills all makes on the system, some of which aren't started by 
you (such as if you're running a build client for other software to help 
building nightlies).
> Or as already said, (ab)use the Execute command and live with the
> opened terminal. IMO the opened terminal for the Execute command should
> stay open, in any case. That is what it is meant for, Lex already said.
> Finally, as also already said, if it is really that important,
> implement it as a plugin and request API additions you need.

I see. I'll just stick to my local hack then.

Best regards.

More information about the Devel mailing list