Zsh Mailing List Archive
Messages sorted by:
Re: zsh and line breaks
- X-seq: zsh-workers 19716
- From: Oliver Kiddle <okiddle@xxxxxxxxxxx>
- To: "Peter A. Castro" <doctor@xxxxxxxxxxxx>
- Subject: Re: zsh and line breaks
- Date: Thu, 01 Apr 2004 11:09:56 +0200
- Cc: zzapper <david@xxxxxxxxxx>, zsh-workers@xxxxxxxxxx, cygwin@xxxxxxxxxx
- In-reply-to: <Pine.LNX.4.53.0403310935450.9892@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <s38u10erwrz.fsf@xxxxxxxxxxxxxxxxxxxx> <1vvf60l9i7n4nlobcroik2le5ofe6v2rn4@xxxxxxx> <Pine.LNX.4.53.0403291441160.5939@xxxxxxxxxxxxxxxxxxxx> <3372.1080639122@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.53.0403301047250.5939@xxxxxxxxxxxxxxxxxxxx> <2603.1080737128@xxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.53.0403310935450.9892@xxxxxxxxxxxxxxxxxxxx>
"Peter A. Castro" wrote:
> > It is easy for us to add `#ifdef __CYGWIN__' around changes or #define
> > O_TEXT to zero on other systems so if you do correct the problem,
> > please send the changes back to us.
> There are about 43 open() calls which I've updated with the O_TEXT
> option. Having all those ifdef's seemed rather ugly (makes the code hard
> to look at, expectially when they are within a few lines of each other)
> so I took a more "elegent" approach, though you may want to revise it if
> it doesn't meet your style requirements :)
I can believe that adding ifdef's to all is ugly. That's what I meant
by "#define O_TEXT to zero on other systems" - just one thought on a
possible more "elegant" approach.
> Yep, I'm experimenting with this right now. As it stands, tests which
> print out to a file and then cat it back in (currently A04redirect and
> E01options) produce a diff, but don't otherwise seem to have any
Are the diffs just the line endings? From what I understand, the
reported problems were with text files used as input to the shell (i.e.
scripts, sourced files, autoloaded functions and stdin). Quite whether
it is also right for redirected output, I wouldn't know.
Messages sorted by: