X-Spam-Check-By: sourceware.org
Date: Mon, 16 Oct 2006 10:36:07 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: lin q <linq936 AT hotmail DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: Can not start UltraEdit using cygwin path
In-Reply-To: <BAY21-F175DFD03F91F9E2EB5F331E9090@phx.gbl>
Message-ID: <Pine.GSO.4.63.0610161032300.13079@access1.cims.nyu.edu>
References: <BAY21-F175DFD03F91F9E2EB5F331E9090 AT phx DOT gbl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sun, 15 Oct 2006, lin q wrote:

> > From: Brian Dessent <brian AT XXXXXXX DOT XXX>
> > Reply-To: cygwin AT XXXXXX DOT XXX
> > To: cygwin AT XXXXXX DOT XXX

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> > Subject: Re: Can not start UltraEdit using cygwin path
> > Date: Sun, 15 Oct 2006 17:34:15 -0700
> >
> > lin q wrote:
> >
> > >   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 know cygpath, but it is easier to just type in DOS path than to use
> cygpath each time.

You already defined a function.  Just add some smarts to it.

> > >   Interesting enough, I have similar function for gvim,
> > >
> > > vi ()
> > > {
> > >     gvim $@ &
> > > }
> >
> > gvim is a Cygwin application.
>
> 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.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/