On Sat, 02 Mar 2013 14:37:46 +0100 Colomban Wendling lists.ban@herbesfolles.org wrote:
I didn't yet started talking about that in the other thread but I did think about it: how do you make a plugin run the execute commands without too ugly hackery in Geany?
First, you can emit a gboolean signal with more data than "build-start", and execute the command in Geany only if no plugin executed it already.
Second, the VTE plugin can define menu items for the execute actions somewhere under "Tools" (with shortcuts of course). So Build -> Execute will run the program with $TERM, and Tools -> VTE -> Execute (for example) will run it in VTE.
Hum. If it is a core plugin, wouldn't it add a dependency on the Geany package? Of course it'd be optional and everything, but not really different than a build-time dependency on Geany itself, would it be?
Personally I thought about putting it in geany-plugins, since debugger, scope and multiterm already depend on libvte, or in a separate plugin.
I don't see yet the huge benefits, mostly because I don't see how to make it have all the same features as current VTE support without adding a whole bunch of hackery.
Execute will require some work, send selection to terminal is easy. I don't think hackery will be required, just some signals and/or extra plugin API functions, and they may be beneficial to the other plugins with vte.