Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-Id: <4.3.1.2.20010206165432.019ede18@pop.ma.ultranet.com>
Date: Tue, 06 Feb 2001 16:57:41 -0500
To: Earnie Boyd <cygwin@cygwin.com>
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Subject: Re: Problem w/ cygwin tar.exe: Unable to tar
  directoriesbeginnin g w/  the letter 'R' in NT 4.0
Cc: cygwin@cygwin.com
In-Reply-To: <3A80684D.48873522@yahoo.com>
References: <4.3.1.2.20010206151048.019a7780@pop.ma.ultranet.com>
 <4.3.1.2.20010206145452.019ba320@pop.ma.ultranet.com>
 <17B78BDF120BD411B70100500422FC6309E1F1@IIS000>
 <4.3.1.2.20010206145452.019ba320@pop.ma.ultranet.com>
 <20010206150831.D9005@redhat.com>
 <4.3.1.2.20010206151048.019a7780@pop.ma.ultranet.com>
 <4.3.1.2.20010206152658.019d2d70@pop.ma.ultranet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 04:10 PM 2/6/2001, Earnie Boyd wrote:
>"Larry Hall (RFK Partners, Inc)" wrote:
> >
> > >Oops.  No, I didn't get you.  You're seeing an echo feature.  It looks like
> > >cygwin is probably doing the right thing.  echo is translating \t to a tab.
> > >I don't believe that cygwin would do this.
> > >
> > >The easiest way to check is to write a simple c program which displays its
> > >arguments.  This will bypass any echo trickery.
> > 
> > Right.  Looks like its not globbing trickery.  A small program prints out
> > the arguments exactly as they're typed.  However, the same trickery
> > that echo uses appears to be what's affecting tar.  So far I've noticed
> > "bad" behavior in both with \t, \r, and \n.  In echo, this is a "feature"
> > I'm sure but in tar, I'd say its a bug.  I'm back to thinking the issue is
> > with tar...
> >
>
>Bug?!?!  The real bug is this thread.  I consider the translation of \r,
>\t, \n, etc. as a specifically stated feature found in all common
>unices.  Now, if we're discussing operation from the cmd.exe/command.com
>shells, and since Cygwin is aware of that fact, Cygwin could double the
>'\' characters it finds in the command line while setting the argv array
>before spawning the program to execute.  This would prevent this natural
>translation.  AFAIK, it may already try to do this and is truly a bug in
>Cygwin if it doesn't; but, this may be an unimplemented feature.


Go back over the thread again.  The "bug" shows up in echo, where its 
considered a feature, and in tar, where its not a feature.  Other utilities
like ls, cat, etc have no problems with this.  Thus, its not a Cygwin bug.
Reviewing the thread should make that clear.  If it doesn't, post your 
specific concern.


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple