On Wed, 30 Oct 2013, Beno?t Minisini wrote:
> Try that. You must kill gnuplot explicitely. Otherwise by running
> the program several times, you get a lot of gnuplot processes all
> writing to the same pipes. So everything is mixed.
>
Seems like occasionally my brain stops working... Thanks for p
On Wed, 2013-10-30 at 00:46 +0100, Benoît Minisini wrote:
> Le 30/10/2013 00:00, Benoît Minisini a écrit :
> > Le 29/10/2013 23:12, Tobias Boege a écrit :
> >> On Fri, 25 Oct 2013, Beno?t Minisini wrote:
> >>> Le 24/10/2013 15:08, Tobias Boege a ?crit :
> My workaround always was like this:
>
Le 30/10/2013 00:00, Benoît Minisini a écrit :
Le 29/10/2013 23:12, Tobias Boege a écrit :
On Fri, 25 Oct 2013, Beno?t Minisini wrote:
Le 24/10/2013 15:08, Tobias Boege a ?crit :
My workaround always was like this:
' Create the read pipe special file
hGPstdout = Pipe "/tmp/gnuplotFI
On Wed, 2013-10-30 at 00:00 +0100, Benoît Minisini wrote:
> Le 29/10/2013 23:12, Tobias Boege a écrit :
> > On Fri, 25 Oct 2013, Beno?t Minisini wrote:
> >> Le 24/10/2013 15:08, Tobias Boege a ?crit :
> >>> My workaround always was like this:
> >>>
> >>> ' Create the read pipe special file
> >>
Le 29/10/2013 23:12, Tobias Boege a écrit :
> On Fri, 25 Oct 2013, Beno?t Minisini wrote:
>> Le 24/10/2013 15:08, Tobias Boege a ?crit :
>>> My workaround always was like this:
>>>
>>> ' Create the read pipe special file
>>> hGPstdout = Pipe "/tmp/gnuplotFIFO2" For Write
>>> Close #hGPs
On Fri, 25 Oct 2013, Beno?t Minisini wrote:
> Le 24/10/2013 15:08, Tobias Boege a ?crit :
> > My workaround always was like this:
> >
> >' Create the read pipe special file
> >hGPstdout = Pipe "/tmp/gnuplotFIFO2" For Write
> >Close #hGPstdout
> >' Create write end
> >hGPpipe = P
On Tue, 29 Oct 2013, Caveat wrote:
> If gnuplot is giving an error, wouldn't that appear on stderr, which you
> don't appear to be watching?
>
> Just a thought...
>
I also had a version where I redirected stdout to stderr had stderr
redirected to the FIFO before. Good thought but no, the text a
If gnuplot is giving an error, wouldn't that appear on stderr, which you
don't appear to be watching?
Just a thought...
Kind regards,
Caveat
On 29/10/13 15:04, Tobias Boege wrote:
> On Fri, 25 Oct 2013, Beno?t Minisini wrote:
>> Le 24/10/2013 15:08, Tobias Boege a ?crit :
>>> My workaround alwa
On Fri, 25 Oct 2013, Beno?t Minisini wrote:
> Le 24/10/2013 15:08, Tobias Boege a ?crit :
> > My workaround always was like this:
> >
> >' Create the read pipe special file
> >hGPstdout = Pipe "/tmp/gnuplotFIFO2" For Write
> >Close #hGPstdout
> >' Create write end
> >hGPpipe = P
On Fri, 2013-10-25 at 02:27 +0200, Benoît Minisini wrote:
> Le 24/10/2013 15:08, Tobias Boege a écrit :
> > My workaround always was like this:
> >
> >' Create the read pipe special file
> >hGPstdout = Pipe "/tmp/gnuplotFIFO2" For Write
> >Close #hGPstdout
> >' Create write end
> >
Le 24/10/2013 15:08, Tobias Boege a écrit :
> My workaround always was like this:
>
>' Create the read pipe special file
>hGPstdout = Pipe "/tmp/gnuplotFIFO2" For Write
>Close #hGPstdout
>' Create write end
>hGPpipe = Pipe "/tmp/gnuplotFIFO1" For Write
>' Start writer
>h
On Thu, 24 Oct 2013, Bruce wrote:
> >From "Stream & input/Output functions"|"PIPE":
>
> 1. If I specify READ WATCH then according to the help "If at least one
> byte can be read from the pipe, then the event handler File_Read() is
> called." but what is the name of event handler. Surely it cant be
>From "Stream & input/Output functions"|"PIPE":
1. If I specify READ WATCH then according to the help "If at least one
byte can be read from the pipe, then the event handler File_Read() is
called." but what is the name of event handler. Surely it cant be
"File_Read"?
2. According to the first exa
13 matches
Mail list logo
