Ah thanks for the quick reply.
Pressing enter after does work.
However, since the security loophole only occurs when "Follow the path of the current file" is enabled, why not make the security feature enabled only when the option is?
Just wondering..
On Mon, Sep 1, 2008 at 11:44 PM, Enrico Tröger enrico.troeger@uvena.dewrote:
On Mon, 1 Sep 2008 23:25:00 +0800, "onguarde -" onguarde@gmail.com wrote:
Hi,
As suggested by someone in the IRC channel, here goes...
Executing programs in VTE does work. However, I keep receiving the following error after a couple of repetitive building and executing of a C source file.
"Could not execute the file in the VTE because it probably contains a command." The error message is shown in the status bar.
I am uncertain what triggers it and upon a restart, I can continue executing/buildings the same source file normally.
this is an intended security feature. See [1] for the whole discussion and reasons why this makes sense. And as Nick and me wrote in [2] this can be simply avoided by pressing Enter after working in the VTE or by restarting it (with SVN => r2920).
[1] http://lists.uvena.de/pipermail/geany/2007-December/002290.html [2]
https://sourceforge.net/tracker/?func=detail&atid=787791&aid=2073061...
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany