zsh-workers
 help / color / mirror / code / Atom feed
From: "Peter A. Castro" <doctor@fruitbat.org>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zzapper <david@tvis.co.uk>, zsh-workers@sunsite.dk, cygwin@cygwin.com
Subject: Re: zsh and line breaks
Date: Tue, 30 Mar 2004 10:54:09 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403301047250.5939@gremlin.fruitbat.org> (raw)
In-Reply-To: <3372.1080639122@trentino.logica.co.uk>

On Tue, 30 Mar 2004, Oliver Kiddle wrote:

> "Peter A. Castro" wrote:
> > > I run zsh on Cygwin, unlike bash zsh gets very upset if it sees dos
> > > returns. I have to run dos2unix on my zsh scripts.
> > >
> > > I haven't seen an explanation for this
> > Hmm... I'll have to look into this.  I thought I'd corrected this for
> > Cygwin...
>
> Are those corrections likely to be limited to the Cygwin package for
> zsh?

Yes.  Currently, my changes are Cygwin specific and really don't apply to
the other platforms.

> I don't use Cygwin myself but from a quick search, it looks like there
> is an O_TEXT flag to open which we could use (a couple of places in
> init.c would cover scripts I think). Wouldn't work where the script
> comes from stdin, though. Does that perhaps help?

I'm aware of O_TEXT and I thought I'd changed all of the places where
files are opened already, but I just checked my patches and those changes
are gone!  AARRGGHH!!  Ok, I'll re-edit and get that back in.  Going
through stdin or via piped fds may be an issue still.  Anyway, thanks for
the thought!

> Oliver

-- 
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
	"Cats are just autistic Dogs" -- Dr. Tony Attwood


  reply	other threads:[~2004-03-30 18:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <s38u10erwrz.fsf@ackusativ.ling.uu.se>
     [not found] ` <1vvf60l9i7n4nlobcroik2le5ofe6v2rn4@4ax.com>
     [not found]   ` <Pine.LNX.4.53.0403291441160.5939@gremlin.fruitbat.org>
2004-03-30  9:32     ` Oliver Kiddle
2004-03-30 18:54       ` Peter A. Castro [this message]
2004-03-31 12:45         ` Oliver Kiddle
2004-03-31 17:53           ` Peter A. Castro
2004-04-01  9:09             ` Oliver Kiddle
2004-04-01 21:20               ` Peter A. Castro
2004-04-02  9:49                 ` Dave Korn
2004-04-02 16:59                   ` Peter A. Castro
2004-04-03  1:23                 ` Peter A. Castro
2004-04-03 20:35                   ` Bart Schaefer
2004-04-04 19:29                     ` Peter Stephenson
2004-04-05 16:19                       ` Peter A. Castro
2004-04-05 17:40                         ` Peter Stephenson
2004-04-05 22:08                           ` Peter A. Castro
2004-04-05 23:08                             ` Clint Adams
2004-04-05 23:25                               ` Peter A. Castro
2004-04-07 21:10                                 ` Clint Adams
2004-04-08  1:16                                   ` Peter A. Castro
2004-04-09  5:00                                     ` Felix Rosencrantz
2004-04-09 16:26                                       ` Peter A. Castro
2004-04-06  9:43                             ` Peter Stephenson
2004-04-06 22:25                               ` Peter A. Castro
2004-04-15  5:03                             ` Clint Adams
2004-04-15  6:43                               ` Peter A. Castro
2004-04-15 10:35                                 ` Clint Adams
2004-04-15 16:57                                   ` Peter A. Castro
2004-04-15 18:14                                     ` Clint Adams
2005-01-31  5:07                             ` Patch for 4.2.3 building on Cygwin Peter A. Castro
2005-01-31 11:37                               ` Peter Stephenson
2005-01-31 20:48                                 ` Peter A. Castro
2005-02-01 10:53                                   ` Peter Stephenson
2005-02-01 16:03                                     ` Bart Schaefer
2005-02-01 18:04                                       ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0403301047250.5939@gremlin.fruitbat.org \
    --to=doctor@fruitbat.org \
    --cc=cygwin@cygwin.com \
    --cc=david@tvis.co.uk \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).