This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problems with @pathnames


Magnus,

The @-file expansion feature is active only when a non-Cygwin program invokes a Cygwin executable.

Try your examples from CMD.exe or COMMAND.exe and you'll see that @-file expansion works as advertised.

Randall Schulz


At 09:11 2003-07-15, Magnus Lewis-Smith wrote:
Do you have to do anything special to turn on @pathname expansion?

The Cygwin User Guide, Chapter 3 (Special Filenames)
[http://cygwin.com/cygwin-ug-net/using-specialnames.html]
states:

Example 3-2. Using @pathname

   bash$ echo  'This   is   "a     long"  line' > mylist
   bash$ echo @mylist
   @mylist
   bash$ /bin/echo @mylist
   This is a     long line
   bash$ rm mylist
   bash$ /bin/echo @mylist
   @mylist


which suggests that it should 'just happen'. However, I get:


   (~) echo  'This   is   "a     long"  line' > mylist
   (~) echo @mylist
   @mylist
   (~) /bin/echo @mylist
   @mylist

which is clearly not what we want. This has only been happening with recent
cygwin1.dlls -- I'm using 1.3.22-1 now. I had an older setup -- long gone now,
but probably 1.2.something where it was working.


Any advice would be appreciated, particularly if I'm doing something really
stupid.

Thanks
Magnus Lewis-Smith


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]