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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 14 Aug 2002 20:55:03 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: RE: @file handling in Cygwin
In-Reply-To: <762C0A863A7674478671627FEAF584812C357A@hqmail01.powertv.com>
Message-ID: <Pine.GSO.4.44.0208142048290.25005-100000@slinky.cs.nyu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

No.  bash and sh were the first things I've tried, and then I vaguely
remembered reading in the User Guide that this feature was added to
overcome the prohibitively short DOS command line limit, which lead me to
try it in the command prompt.
	Igor

On Wed, 14 Aug 2002, Cheng, Cheuk wrote:

> Thanks Igor.  Did you get the same thing to work within bash or sh?  The
> example in the Cygwin User Guide actually uses an @file inside bash as a
> demonstration.
>
> cheng AT powertv DOT com
>
> -----Original Message-----
> From: Igor Pechtchanski [mailto:pechtcha AT cs DOT nyu DOT edu]
> Sent: Wednesday, August 14, 2002 4:05 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: @file handling in Cygwin
>
>
> On Wed, 14 Aug 2002, Jon LaBadie wrote:
>
> > On Wed, Aug 14, 2002 at 03:01:55PM -0700, Cheng, Cheuk wrote:
> > > Thanks all for their comments.  Using ls -@lsflags will give "ls:
> > > invalid option -- @" instead.  I also know of cat and xargs but I
> > > just want to check whether @file is supported _within_ Cygwin or
> > > not.
> >
> > Where is it supported?  I've never seen it?
> >
> > Is it an "os" or "shell" feature so that it is not "ls" specific?
> >
> > Otherwise I'd think an ls(1) man page perusal would answer the
> > question negatively.
>
> This feature works when cygwin programs are invoked from the windows
> command shell:
>
> C:\cygwin\tmp\testls>type files
> files lsflags
>
> C:\cygwin\tmp\testls>type lsflags
> -a --color
>
> C:\cygwin\tmp\testls>ls -l @files
> -rw-rw-rw-    1 igor     None           14 Aug 14 19:03 files
> -rw-rw-rw-    1 igor     None           11 Aug 14 19:02 lsflags
>
> C:\cygwin\tmp\testls>ls @lsflags
> .  ..  files  lsflags
>
> C:\cygwin\tmp\testls>
>
>         Igor

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

It took the computational power of three Commodore 64s to fly to the moon.
It takes a 486 to run Windows 95.  Something is wrong here. -- SC sig file


--
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/