From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-5766-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 5256 invoked from network); 20 Jan 2003 11:36:46 -0000
Received: from sunsite.dk (130.225.247.90)
  by ns1.primenet.com.au with SMTP; 20 Jan 2003 11:36:46 -0000
Received: (qmail 28698 invoked by alias); 20 Jan 2003 11:36:21 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 5766
Received: (qmail 28689 invoked from network); 20 Jan 2003 11:36:21 -0000
X-MessageWall-Score: 0 (sunsite.dk)
From: Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
To: "'Le Wang'" <lewang@yahoo.com>, "'Zsh users list'" <zsh-users@sunsite.dk>
Subject: RE: cygwin + /dev/stderr
Date: Mon, 20 Jan 2003 14:36:13 +0300
Message-ID: <6134254DE87BD411908B00A0C99B044F03A0B5E4@mowd019a.mow.siemens.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
In-Reply-To: <20030119231354.35178.qmail@web12303.mail.yahoo.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106


> Hi all,
> 
> I use /dev/stderr in my scripts profusely.  Now that I
> started using cygwin, these scripts would generally
> fail.  I understand that Bash has built in /dev/*
> handling for cygwin, is there any plans for ZSh to
> develop similar features?
> 

/dev/stderr is not and never has been portable. Any script that relies on
that is flawed as you just discovered.

> What's the best way for me to handle this without
> modifying all of my scripts?
> 

The best way would still be to modify your scripts to avoid this problem in
future :) Who knows, may be you will use another Unix someday.

What version of Cygwin are you using? I have vague memory that Cygwin
emulates /dev/std* as well but may be wrong here.


-andrej