Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <20030715161139.63988.qmail@web14909.mail.yahoo.com> Date: Tue, 15 Jul 2003 17:11:39 +0100 (BST) From: =?iso-8859-1?q?Magnus=20Lewis-Smith?= Subject: Problems with @pathnames To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ -- 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/