On Sat, 16 Nov 2013 15:12:03 -0800
Matthew Brush mbr...@codebrainz.ca wrote:
It's an on-going effort to improve the situation with process spawning
on Win32 in Geany core for [...] build commands and such.
BTW, the patched build.c runs the build [non-execute] commands without
sh. I'm not sure
I'm not familiar with what this is about? I'm away from my computer to look at
the code. Is this a plugin to run/spawn external programs and capture output?
If so, you may want to check out my external-tools plugin:
On 13-11-16 02:20 PM, Steven Blatnick wrote:
I'm not familiar with what this is about? I'm away from my computer to look at
the code. Is this a plugin to run/spawn external programs and capture output?
If so, you may want to check out my external-tools plugin:
On Mon, 04 Nov 2013 21:33:36 +0100
Thomas Martitz thomas.mart...@student.htw-berlin.de wrote:
Am 04.11.2013 19:04, schrieb Dimitar Zhekov:
On Mon, 4 Nov 2013 09:44:45 +1100
Lex Trotman ele...@gmail.com wrote:
I propose to always create the win~1 programs with a minimized,
non-focused
On Mon, 4 Nov 2013 09:44:45 +1100
Lex Trotman ele...@gmail.com wrote:
I propose to always create the win~1 programs with a minimized,
non-focused window. For console programs, the uncaptured output will
go to the console, and will be lost when the console is auto closed
by win~1, but
Hi again,
Win~1 supports some weird command line syntaxises:
c:\some path\program.exe - without closing quote
c:\some path\program.exefoo bar qux - runs program.exe with:
argv[0] = c:\some path\program.exefoo (or something similar)
argv[1] = bar
argv[1] = qux
I'm going to disallow the first
