Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 13 Mar 2003 16:51:24 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Mixing / and \ path separators Message-ID: <20030313215124.GB4634@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <79218202D4B9D4118A290002A508E13B79C3B8@pnzexchange.pharos-intranet.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79218202D4B9D4118A290002A508E13B79C3B8@pnzexchange.pharos-intranet.co.nz> User-Agent: Mutt/1.5.1i On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote: >> From: Christopher Faylor [mailto:cgf-cygwin@cygwin.com] >> >> On Wed, Mar 12, 2003 at 11:08:27PM +0100, Anton Ertl wrote: >> > >> >If so, how should I deal with path names where parts of the path come >> >from ordinary windows users? >> >> Either tell your Windows users to use forward slashes, tell them to >> specify the path name using windows specs like f:\cygwin\foo\bar, >> or change the backslashes to slashes. > >Wouldn't cygwin_conv_to_posix_path() and its relatives be a more >general solution? Good point. It probably is, if that option is available. 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/