Actually, this may turn into a can of worms, so comments would be useful.
Search for "can of worms" in ecore_exe.c for some commentary. Personally,
I worry that we may have gone overboard, polling is bad 'mkay.
SVN revision: 19859
* both exe run functions now use the same code.
* don't allocate pipes that wan't be used. This made the code much cleaner.
* track and free the exe timers as needed.
E still reports a naughty null timer free at shutdown time, but I don't
think its in ecore_exe. I'll valgrind it later.
The error fd handler is curently an identical copy of the read fd handler,
with only the names changed. That's a big slab of code that is duplicated.
I'll merge the two into something generic next.
raster also mentioned that say the first ten lines or so of stderr should
be thrown into a dialog and shown to the user. I don't know if there is a
way to do that from ecore, or if the user of ecore_exe has to do that
themselves. The stderr support does line buffered mode just like the read
support, but has not been tested yet. I'll test properly after the merge.
SVN revision: 19700
Check it's pulse, hold a mirror to it's mouth, check for brain activity.
Pump another round or two into it, cut off it's head, put a stake through
it's heart.
Sprinkle holy water over it's corpse, hold a black mass to ask Lucifer if
it turned up in hell yet, consult the entrails of rasters three headed
chicken.
If all else fails, complain that the bitch is still alive, and stronger
measures will be needed.
SVN revision: 19475
metacharacters present in the command line passed. If there aren't any, parse
command line to arguments and pass to execvp instead of calling `sh -c' with the
entire command line. Hope we have covered all cases in which sh -c should be
necessarily invoked :) The current approach is pretty conservative though -
anything suspicious, and over to sh.
SVN revision: 18705
Don't use ecore_exe_pipe_run() yet, it is not finished. You can use
ecore_exe_pipe_write(), but it will do nothing. I committed this
because someone wanted to play with it in it's current state.
ecore_exe_pipe_run() will startup your exe, and open the pipes that you
request, and everything should get cleaned up when the exe closes. The
pipes are in the Ecore_Exe struct, you can use them. The next thing I
will add will be proper use of the pipes.
SVN revision: 18400
execle functions can be thought of as arg0, arg1, ..., argn. Together
they describe a list of one or more pointers to null-terminated strings
that represent the argument list available to the executed program.
The first argument, by convention, should point to the file name asso-
ciated with the file being executed. The list of arguments must be
terminated by a NULL pointer, and, since these are variadic functions,
this pointer must be cast (char *) NULL.
SVN revision: 14411
David Walter Seikel
Carsten Haitzler
andyetitmoves
sebastid
tsauerbeck
ncn
xcomputerman