[Geany-devel] ANN: Configurable Build Menu Alpha in SVN
elextr at xxxxx
Mon Aug 17 03:42:27 UTC 2009
I think we agree but are saying it differently. Let me re-state it
1. Killing all the child build processes is significant but not
impossible work and implementing it in C isn't very portable.
2. Even if we were willing to do the work involved in 1, killing a
build is risky because Geany does not know what the build might be
doing and what problems killing it may cause.
3. As we agree, this is the problem of the build script creator and
you are right to blame them
4. But the user of Geany is not always the creator of the build
script. They just grabbed a useful looking program from an SVN
repository and edited and built it All goes well until they try to
kill a build and they may get problems that they are not expecting or
to blame for. This is not nice :-( Many will blame Geany for
providing the kill command.
5. But killing a build is useful if you know what you are doing, so
having an external script available for such users to configure into
their Geany is useful. I encourage you to write the safest possible
and most portable one. And if its invoked by the execute menu items
it is configurable by filetype, project, user config etc. so the user
can even limit when it is available to the smallest safe subset.
2009/8/17 Thomas Martitz <thomas.martitz at student.htw-berlin.de>:
> Lex Trotman schrieb:
>>>> It may not be the users build script, for example, have you checked
>>>> fully what Geany's make does??? I havn't even looked at it :-)
>>> For those we can make sure it doesn't harm to kill those. Otherwise I
>>> consider this as an actual bug in Geany.
>> Sorry, I'm not quite sure I understand your comment, I'm sure you are
>> not saying its a bug in Geany if a users build script behaves badly??
> You were the one referring to Geany's built-in default commands, so was I.
> Btw, you just said it yourself. Of course Geany isn't on fault if a user
> script is damaged, the author of the script is. That's what I'm saying the
> whole time. That's why we can blame the user for it's scripts.
>>> That's like not implementing system calls in a operating system. Just
>>> because one can write harmful software using system calls?
>> Yeah but system calls arn't available at user level.
> Anyone can call system calls in every program no matter of the level.
> Geany-devel mailing list
> Geany-devel at uvena.de
More information about the Devel