> Date: Fri, 15 Dec 2006 16:14:38 +0100 (CET) > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-devel@gnu.org, > emacs-pretest-bug@gnu.org > From: Werner LEMBERG <[EMAIL PROTECTED]> > > Since those issues are full of subtleties I suggest that you have a > look at the gnulib CVS (at savannah.gnu.org), inspecting the files > `execute.c' and `pipe.c': > > > http://cvs.savannah.gnu.org/viewcvs/gnulib/lib/execute.c?rev=1.7&root=gnulib&view=log > > http://cvs.savannah.gnu.org/viewcvs/gnulib/lib/pipe.c?rev=1.6&root=gnulib&view=log
Thanks, but I see nothing in these source files that could shed any light on the case in point. > Similar code is used in groff too. Groff builds a pipe of several programs and then runs that pipe. By contrast, emacsclient needs to run a single program, and doesn't need to read/write its standard streams. So the complexity of the above URLs is not needed. _______________________________________________ emacs-pretest-bug mailing list emacs-pretest-bug@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
