<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top"><p>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?</p>
<p>If so, you may want to check out my external-tools plugin:</p>
<p> https://github.com/sblatnick/geany-plugins/tree/external-tools/external-tools/src </p>
<p>Thanks,</p>
<p>Steve</p>
</td></tr></table> <div id="_origMsg_">
<div>
<br />
<div>
<div style="font-size:0.9em">
<hr size="1">
<b>
<span style="font-weight:bold">From:</span>
</b>
Dimitar Zhekov <dimitar.zhekov@gmail.com>; <br>
<b>
<span style="font-weight:bold">To:</span>
</b>
Geany development list <devel@lists.geany.org>; <br>
<b>
<span style="font-weight:bold">Subject:</span>
</b>
[Geany-Devel] spawning rewrite - RFC <br>
<b>
<span style="font-weight:bold">Sent:</span>
</b>
Sat, Nov 16, 2013 3:26:51 PM <br>
</div>
<br>
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top">Hi,<BR><BR>The attached archive contains:<BR><BR>- spawn.[ch] - spawning functions and tests, not Geany-dependent<BR>- Makefile - to compile the spawning tests under *nix/win~1<BR>- emit.c - a useful program to spawn<BR>- spawn.rsp - as in "./spawn < spawn.rsp"<BR>- respawn.diff - patch for Makefile.am, build.c and tools.c<BR><BR>I can patch search.c as well, if we agree on "grep --exclude-dir"<BR>for the non-recursive searches instead of finding and passing the<BR>file names manually, as explained in the "Improving FiF" thread. If<BR>we don't, or start some endless discussion, feel free to replace<BR>the current mess with a smaller one.<BR><BR>tools.c should probably use spawn_sync(..., gchar *stdout, gchar<BR>*stderr, gint *exit_status), but I haven't written one yet.<BR><BR>If the spawned program emits mixed stdout and stderr messages fast,<BR>like emit.c, they will be grouped, depending on
the size of your pipe<BR>buffers. Doesn't seem a problem in practice - the tons of messages<BR>from making Geany with -Wall -WExtra are OK, and running ./autogen.sh<BR>is fine too.<BR><BR>Note that there is no conversion to UNICODE under win~1. Using the<BR>"ANSI" functions is OK AFAICT, make/grep/gcc are all "ANSI" programs,<BR>and the only thing an ansi -> unicode -> ansi conversion does is to<BR>produce errors such as "Create process failed, unable to encode byte<BR>at offset xyz" (win~1 FiF with non-UFT-8 fails regularily).<BR><BR>-- <BR>E-gards: Jimmy<BR></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>