X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Tue, 2 Mar 2010 14:18:35 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin 1.7.1: "bash prompt here" can't be used at directory which's name contains unicode charactor. Message-ID: <20100302191835.GC13535@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <40399aed1003020442q4f49b811h41bd4064072762a5@mail.gmail.com> <4B8D5C9D.9040906@gmail.com> <20100302185009.GE12665@ednor.casa.cgf.cx> <4B8D5FA3.10103@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B8D5FA3.10103@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tue, Mar 02, 2010 at 06:57:39PM +0000, Dave wrote: >Christopher Faylor wrote: >> On Tue, Mar 02, 2010 at 06:44:45PM +0000, Dave wrote: >>> Also, is the d:\ within quotes later in the command erronously >>> triggering the nodosfile warning? I'm not expecting to see it here. >> >> I guess this is a FAQ. The error message comes from an attempt to do a >> file access using an MS-DOS path. It does not come from random use of >> backslashes in the command line. >> >> If you see the error then something is trying to use MS-DOS paths. > >That's what I thought, but the command that's being run doesn't have an >MSDOS path except as an argument to the script that bash couldn't find: I'm telling you how Cygwin is written. Someone else will have to help track down what's causing Cygwin to see an MS-DOS path. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple