|
From: Hans-Bernhard B. <br...@ph...> - 2004-05-17 10:22:09
|
On Sun, 16 May 2004 li...@co... wrote: > At this point, I'm not sure if it's the OS or wgnuplot_pipes. The latter. The OS (or more precisely: the command line shell) should know what to do with 2>. > Are there any docs for wgnuplot_pipes, or shall I inspect the source? I'm not aware of any docs other than what Petr may have put into the README of the binary package. > Given what I've read about wgnuplot_pipes, it seems like this would be a > pretty standard use-case, it's a shame to have my hopes dashed at this > point, but I've lived this long without it, I suppose I can continue ;-). Actually, the major use case is to have a gnuplot on Windows that supports piping from within, as in back-tick expansion, data file filtering and output to pipes: set title `my_title_generator` set out "| lpr -P myprinter" plot '< awk -f myscript datafile' The fact that it causes wgnuplot to display a console is a side-effect of the actual modification. In the end, I suspect we'ld have to rewrite large parts of, possibly the entire MS Windows text output routines in gnuplot (i.e. src/win/wtext.c). I once started down that road, but never made it very far, and didn't publish the results. -- Hans-Bernhard Broeker (br...@ph...) Even if all the snow were burnt, ashes would remain. |