|
From:
<br...@ph...> - 2006-04-20 11:13:49
|
Mojca Miklavec wrote: > On 4/18/06, Hans-Bernhard Bröker wrote: >> Mojca Miklavec wrote: >>> I have a gnuplot.bat with >>> c:\path-to-wgnuplot.exe %* >> Calling that batch file gnuplot.bat instead of wgnuplot.bat is creating >> smoke screen that hides the crucial detail: that you're doing this on MS >> Windows. > > I'm sorry that I forgot to mention that. I wasn't aware that gnuplot > in windows behaves differently from the rest of the terminals in this > respect. It's not the terminal that behaves differently --- it's the console that handles text I/O for the gnuplot command line. Windows originally didn't have the notion of a console program at all, back when gnuplot was ported to this platform (16-bit Windows 3.x). So the people back then had to create their own poor-man's equivalent of xterm: the wgnuplot text window. This is a graphical window handling non-graphical text input and output. But it has no connection to the concept of a stdin or stdout channel. I've been working on and off on a re-write of this part of the Windows port, to use a genuine Win32 console instead of our home-grown one. If that ever bears fruit, it'll solve this problem. Until then, you can't wgnuplot to pipe in or out. > So is there any remedy for that? Could I set any variable which will > explicitely tell gnuplot to ignore pauses? No. > How can I compile gnuplot so that I would get pgnuplot instead of > wgnuplot? You can't. pgnuplot is not a variant of wgnuplot, it's built as a separate, small program that communicates with wgnuplot. If you want a fully console-compatible gnuplot on Win32, you have to get the Cygwin binary. The delivered package of that uses and requires X11, but you can also build a console-only one by disabling X11. |