Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: tcp_read -d and newlines

X-seq: zsh-workers 26824
From: Clint Adams <clint@xxxxxxx>
To: Peter Stephenson <pws@xxxxxxx>
Subject: Re: tcp_read -d and newlines
Date: Tue, 7 Apr 2009 18:01:45 +0000
Cc: zsh-workers@xxxxxxxxxx
In-reply-to: <20090406095901.297232b0@news01>
Mail-followup-to: Peter Stephenson <pws@xxxxxxx>, zsh-workers@xxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20090405231036.GA13802@xxxxxxxx> <20090406095901.297232b0@news01>

On Mon, Apr 06, 2009 at 09:59:01AM +0100, Peter Stephenson wrote:
> 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.  It sounds like your
> problem is when there is an EOF.

Yes, I've had some mysteriously loss before but in this case I was
definitely able to confirm that the transmission ended in not-a-newline.
read processes the data, but returns an error so tcp_read tosses it.

I don't actually need the input broken up into lines, so maybe I should
be doing this differently.

References:
- tcp_read -d and newlines
  - From: Clint Adams
- Re: tcp_read -d and newlines
  - From: Peter Stephenson

Messages sorted by: Reverse Date, Date, Thread, Author