From: "Peter A. Castro" <doctor@fruitbat.org>
To: zzapper <david@tvis.co.uk>
Cc: zsh-users@sunsite.dk, cygwin@cygwin.com
Subject: Re: zsh and line breaks
Date: Mon, 29 Mar 2004 14:46:15 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.53.0403291441160.5939@gremlin.fruitbat.org> (raw)
In-Reply-To: <1vvf60l9i7n4nlobcroik2le5ofe6v2rn4@4ax.com>
On Mon, 29 Mar 2004, zzapper wrote:
> On Wed, 24 Mar 2004 18:16:00 +0100, wrote:
>
> >I'm having some trouble with zsh (4.0.6) and line breaks. It seems that
> >it does not accept "\n" as a line break. This results in some
> >uncomfortableness when using it as a login shell, such as this output
> >from Emacs:
> >
> >[bkhl@ackusativ ~/kurser/vt04/lp1/lab1]% latex \\nonstopmode\\input rapport.tex
> >latex \\nonstopmode\\input rapport.tex\n
> >
> >Apparently, zsh is not interpreting \n as EOL.
> >
> >Is there some setting that might fix this?
>
> 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...
One thing, are you running your scripts off of a text or binary mount
filesystem? And, are you running in DOS or Unix mode? I'll need to know
which combinations don't work.
> zzapper (vim, cygwin, wiki & zsh)
--
Peter A. Castro <doctor@fruitbat.org> or <Peter.Castro@oracle.com>
"Cats are just autistic Dogs" -- Dr. Tony Attwood
next prev parent reply other threads:[~2004-03-29 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 17:16 Björn Lindström
2004-03-24 18:44 ` Bart Schaefer
2004-03-29 10:53 ` zzapper
2004-03-29 22:46 ` Peter A. Castro [this message]
2004-03-30 7:35 ` zzapper
2004-03-30 18:46 ` Peter A. Castro
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.0403291441160.5939@gremlin.fruitbat.org \
--to=doctor@fruitbat.org \
--cc=cygwin@cygwin.com \
--cc=david@tvis.co.uk \
--cc=zsh-users@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).