Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: Re: Superfluous CRs trouble completion routines in Cygwin
- X-seq: zsh-workers 21909
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: "Peter A. Castro" <doctor@xxxxxxxxxxxx>
- Subject: Re: PATCH: Re: Superfluous CRs trouble completion routines in Cygwin
- Date: Sun, 23 Oct 2005 19:11:05 +0000
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <Pine.LNX.4.60.0510231021530.5875@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <87irvzys44.fsf@xxxxxxxxxxxxxxxx> <1051015180240.ZM22900@xxxxxxxxxxxxxxxxxxxxxxx> <1051016002252.ZM23495@xxxxxxxxxxxxxxxxxxxxxxx> <87y84owe0f.fsf@xxxxxxxxxxxxxxxx> <1051020145129.ZM2623@xxxxxxxxxxxxxxxxxxxxxxx> <87d5lzw13l.fsf@xxxxxxxxxxxxxxxx> <1051021154525.ZM7511@xxxxxxxxxxxxxxxxxxxxxxx> <EXCHANGE03cOpnTvjsE000079cb@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.60.0510231021530.5875@xxxxxxxxxxxxxxxxxxxx>
On Oct 23, 10:33am, Peter A. Castro wrote:
}
} Since we are talking about console input, though, there may be a tty
} setting to control weither CRs are passed to the input stream. I'll see
} if I can investigate this.
I'm not all that familiar with how Cygwin simulates UNIX pipelines. We
are talking about command output piped to the "read" builtin -- is that
the same as console input?
In any case, stripping CRs from the i/o stream would only mask the
problem. It'd be at least as helpful to know why adding a CR to the
IFS value causes a segmentation fault.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author