Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <8B8C8B6AEC2C6B4DA7862541B84050875EFC4B@MPSMSG04.us.schp.com>
From: "Barillier, Michael" <michael DOT barillier AT spcorp DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Bash backquote bug?
Date: Wed, 8 Jan 2003 15:44:46 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"

While running a configure script under bash-2.05b, I observed a bug (?)
similar to the following:

  $ ls configure*
  configure  configure.in
  $ echo timestamp >conftest.file
  $ ls -Lt ./configure conftest.file
  conftest.file  ./configure
  $ set X `ls -Lt ./configure conftest.file`
  $ echo $*
  X conftest.file ./configure ./configure.in

So, it appears that `ls' produces different output when evaluated at the
command prompt and when run under backquote.  Any ideas?

-- mjb


*********************************************************************
This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/