Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Mon, 22 Apr 2002 21:14:32 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Cc: vim-dev@vim.org Subject: Re: small inter-operability patch for vim 6.1.2 for Cygwin Message-ID: <20020422211432.C7762@cygbert.vinschen.de> Mail-Followup-To: cygwin@cygwin.com, vim-dev@vim.org References: <200204221835.g3MIZoU02673@moolenaar.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i On Mon, Apr 22, 2002 at 03:08:07PM -0400, Chris Metcalf wrote: > > Or better: Isn't there a cygwin trick for this already? > > Well, "cygpath -u PATH" will convert a Windows path to a Unix path. > However, this means you can't just set $EDITOR to a simple executable, > but have to walk it through a script (or dedicated binary) first. > Also, it just seems wrong that vim doesn't handle a Windows path > plausibly, when almost all of the other Cygwin tools do. However, I don't see the problem in using `cygpath'. It's designed for that purpose. I'm not quite sure if it makes sense to tweak vim if there are already tools which do what you want. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin@cygwin.com Red Hat, Inc. -- 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/