X-Spam-Check-By: sourceware.org Date: Mon, 16 Oct 2006 15:37:12 -0700 From: Gary Johnson To: cygwin@cygwin.com Subject: Re: Can not start UltraEdit using cygwin path Message-ID: <20061016223712.GA14954@suncomp1.spk.agilent.com> Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.12 (2006-07-14) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk 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 2006-10-16, Igor Peshansky wrote: > On Sun, 15 Oct 2006, lin q wrote: > > I download gvim myself from vim web site and installed it, it is not the > > one in cygwin package. This is the reason I think the application does > > not have to be from cygwin package. > > The application has to be a Cygwin *program* to understand POSIX paths, > but not necessarily a Cygwin package. However, even if the gvim you've > installed is not a Cygwin program, it may simply serve as a shell around > the existing vim installation (and pass the paths to vim unchanged), so if > the vim it picks up is the one that comes with Cygwin, it will understand > POSIX paths. The Windows vim available from the vim web site does its own conversion of POSIX paths to Windows paths. This makes it easier for Unix users who are used to typing forward slashes and allows users to avoid the question of whether backslashes in file names will be interpreted as path separators or as quotes of the following characters. It doesn't understand cygwin paths, however, which is an advantage to using the Cygwin vim. I use both. Regards, Gary -- Gary Johnson | Agilent Technologies garyjohn@spk.agilent.com | Wireless Division | Spokane, Washington, USA -- 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/