Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 3 Oct 2005 12:40:02 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygpath feature suggestion
Message-ID: <20051003164002.GG2270@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <31DDB7BE4BF41D4888D41709C476B6575690BF AT NIHCESMLBX5 DOT nih DOT gov>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <31DDB7BE4BF41D4888D41709C476B6575690BF@NIHCESMLBX5.nih.gov>
User-Agent: Mutt/1.5.8i

On Mon, Oct 03, 2005 at 12:34:58PM -0400, Buchbinder, Barry (NIH/NIAID) wrote:
>It would be useful if cygpath could work as a filter, taking in lists of
>paths on the standard input and put them out one per line on the standard
>output.  This could be used as a work-around for 
>	for F in
>`command_or_pipe_creating_a_list_of_files_with_spaces_in_them`
>	do
>		echo ${F}
>	done
>causing the file names to be split up at the spaces.
>
>Yes, I know, PTC, but I'm not a programmer.  This is just a suggestion.

In this case, the only PTC required is for the documentation.  Take a look
at 'cygpath --help', the option already exists.  It is just not in the man
page.

cgf

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