From: "Peter A. Castro" <doctor@fruitbat.org>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: Superfluous CRs trouble completion routines in Cygwin
Date: Sun, 23 Oct 2005 10:33:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0510231021530.5875@gremlin.fruitbat.org> (raw)
In-Reply-To: <EXCHANGE03cOpnTvjsE000079cb@exchange03.csr.com>
On Fri, 21 Oct 2005, Peter Stephenson wrote:
> Bart Schaefer wrote:
>> ?? I just don't see any reason why $'\r' would be magical.
>
> It's a bit magical in Cygwin depending on whether you've told it to
> translate ends of lines in the file system. No idea if that's
> relevant or not.
For the Cygwin port, I'd updated Src/main.c to use a Cygwin specific
"feature" to force all read-only files opened by the shell to strip out
CRs. This was necessary for reading shell scripts which might have been
created with dos carriage-control.
Unfortinately, this only applies to read-only files (opened with
O_RDONLY), allowing for files opened for write to be influenced by the
filesystem settings. Since the console stream is r/w, the above
"feature" doesn't apply.
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.
> pws
--
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:[~2005-10-23 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87irvzys44.fsf@trews52.bothi.fi>
[not found] ` <1051015180240.ZM22900@candle.brasslantern.com>
2005-10-16 0:22 ` Bart Schaefer
2005-10-17 9:29 ` Peter Stephenson
2005-10-20 12:48 ` Hannu Koivisto
2005-10-20 14:51 ` Bart Schaefer
2005-10-21 11:39 ` Hannu Koivisto
2005-10-21 15:45 ` Bart Schaefer
2005-10-21 16:18 ` Peter Stephenson
2005-10-23 17:33 ` Peter A. Castro [this message]
2005-10-23 19:11 ` Bart Schaefer
2005-10-24 4:34 ` 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.60.0510231021530.5875@gremlin.fruitbat.org \
--to=doctor@fruitbat.org \
--cc=pws@csr.com \
--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).