From 729c92aaa76aa01a3406d2f0c297ae0ef6f5ce7f Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Wed, 13 Feb 2013 17:57:19 +0000 Subject: [PATCH] * pathnames.sgml: Clarify '@' processing. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/pathnames.sgml | 10 +++++----- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index a0d967da8..2839ad9d8 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,7 @@ +2013-02-13 Christopher Faylor + + * pathnames.sgml: Clarify '@' processing. + 2013-01-23 Christopher Faylor * faq-programming.xml: Remove reference to "make check". diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml index 5860ebb0b..77f47a259 100644 --- a/winsup/doc/pathnames.sgml +++ b/winsup/doc/pathnames.sgml @@ -987,19 +987,19 @@ If a registry key contains a subkey and a value with the same name The @pathnames To circumvent the limitations on shell line length in the native -Windows command shells, Cygwin programs expand their arguments +Windows command shells, Cygwin programs, when invoked by non-Cygwin processes, expand their arguments starting with "@" in a special way. If a file pathname exists, the argument @pathname expands recursively to the content of pathname. Double quotes can be used inside the file to delimit strings containing blank space. -In the following example compare the behaviors of the bash built-in -echo and of the program /bin/echo. +In the following example compare the behaviors +/bin/echo when run from bash and from the Windows command prompt. Using @pathname -bash$ echo 'This is "a long" line' > mylist -bash$ echo @mylist +bash$ @/bin/echo 'This is "a long" line' > mylist +bash$ /bin/echo @mylist @mylist bash$ cmd c:\> c:\cygwin\bin\echo @mylist