This is the mail archive of the
mailing list for the Cygwin project.
Re: Can not start UltraEdit using cygwin path
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 15 Oct 2006 22:40:58 -0400
- Subject: Re: Can not start UltraEdit using cygwin path
- References: <BAY21-F175DFD03F91F9E2EB5F331E9090@phx.gbl>
- Reply-to: cygwin at cygwin dot com
lin q wrote:
From: Brian Dessent
lin q wrote:I know cygpath, but it is easier to just type in DOS path than to use
cygpath each time.
> If I run it with cygwin path like this,
> uedit /cygdrive/c/tmp/log
> UltraEdit says the path is wrong.
UltraEdit is not a Cygwin application. How on earth do you expect it to
understand something beginning in /cygdrive? Look into cygpath.
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.
> Interesting enough, I have similar function for gvim,
> vi ()
> gvim $@ &
gvim is a Cygwin application.
One non-Cygwin application that you may have been able to get to understand
some POSIX path does not mean any or all non-Cygwin applications will
understand all POSIX paths. As Brian points out, you should not expect
non-Cygwin applications to understand POSIX paths. If you want such ability,
you will need to build such applications with Cygwin's gcc/g++ (without the
-mno-cygwin flag). FWIW, there is a gvim package for Cygwin. This certainly
understand POSIX paths.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html