Re: reading from input pipe is slow?

Hi Thomas, Thomas Danckaert writes: > I've notice that reading a child process' stdout from a port opened > with (open-input-pipe "command") is very slow. In fact, it's faster > to redirect the child process' output to a temporary file, and then > read this temporary file from Guile, than to di

Re: Re: How to notice abrupt tcp connection losses in server/client?

On 22.06.2018 18:00, guile-user-requ...@gnu.org wrote: > Message: 2 > Date: Fri, 22 Jun 2018 00:09:16 +0100 > From: Chris Vine > To: guile-user@gnu.org > Subject: Re: How to notice abrupt tcp connection losses in > server/client? > Message-ID: <20180622000916.e5180d431446d15843d3f...@gmail.c

Re: GNU Foliot 0.9.8 is released

Joshua Branson writes: > Hmmm. This is the first that I am seeing this. I'm assuming that this > is not really designed to be a free software scheduling solution... > > This is slightly off topic, but is anyone aware of an open source > scheduling solution. My boss currently writes the schedul

reading from input pipe is slow?

Dear guile users, I've notice that reading a child process' stdout from a port opened with (open-input-pipe "command") is very slow. In fact, it's faster to redirect the child process' output to a temporary file, and then read this temporary file from Guile, than to directly read the child p

Re: How to notice abrupt tcp connection losses in server/client?

On Fri, 22 Jun 2018 09:27:30 +0300 Eli Zaretskii wrote: > > Date: Fri, 22 Jun 2018 00:09:16 +0100 > > From: Chris Vine > > > > I think you will need to use recv! with windows, because you cannot > > read from sockets in windows using POSIX read(). > > What makes you say that? It isn't true; Ga