Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: tcp_read -d and newlines
- X-seq: zsh-workers 26812
- From: Peter Stephenson <pws@xxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: tcp_read -d and newlines
- Date: Mon, 6 Apr 2009 10:10:55 +0100
- In-reply-to: <20090406095901.297232b0@news01>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Organization: CSR
- References: <20090405231036.GA13802@xxxxxxxx> <20090406095901.297232b0@news01>
On Mon, 6 Apr 2009 09:59:01 +0100
Peter Stephenson <pws@xxxxxxx> wrote:
> On Sun, 5 Apr 2009 23:10:36 +0000
> Clint Adams <clint@xxxxxxx> wrote:
> > When tcp_read -d'ing a socket that doesn't end in a newline, the last
> > "line" gets discarded, I think, because read returns an error on that
> > line.
>
> I've had problems with this, too, in the past, although I think my problem
> was chunks of input (not necessarily ending in EOF) that didn't have
> newlines. I could find an easy way of handling this.
\
n't, sorry. Probably obvious from the context but I
thought I'd better correct it.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author