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 Date: Thu, 13 Mar 2003 16:56:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Mixing / and \ path separators Message-ID: <20030313215648.GA5157@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <79218202D4B9D4118A290002A508E13B79C3B8 AT pnzexchange DOT pharos-intranet DOT co DOT nz> <20030313215124 DOT GB4634 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030313215124.GB4634@redhat.com> User-Agent: Mutt/1.5.1i On Thu, Mar 13, 2003 at 04:51:24PM -0500, Christopher Faylor wrote: >On Fri, Mar 14, 2003 at 08:46:13AM +1300, Ross Smith wrote: >>> From: Christopher Faylor [mailto:cgf-cygwin AT cygwin DOT 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. I'm sorry. No. Let me take that back. I think what is being done is that someone is typing /usr\local/bin. cygwin_conv_to_posix_path is not the right solution here. That would end up creating something like /cygdrive/c/usr/local/bin which is probably not what's intended. 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/