Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 2 Nov 2001 00:37:23 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Supressing @path expansion Message-ID: <20011102003723.C26768@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3BE0F97A DOT 93A18F26 AT email DOT byu DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BE0F97A.93A18F26@email.byu.edu> User-Agent: Mutt/1.3.21i On Thu, Nov 01, 2001 at 12:27:54AM -0700, Eric Blake wrote: >I'm wondering if there is a way to make a cygwin-compiled program always >receive its @pathname arguments unexpanded. The '@' processing is invoked when a cygwin application is run from a non-cygwin app but is ignored when running a cygwin program via a cygwin program. So, this will work: bash% echo @foo This won't: c:\> c:\cygwin\bin\echo @foo However, quoting the '@argument' should stop this behavior: c:\> c:\cygwin\bin\echo '@foo' cgf -- 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/