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 Message-ID: X-Originating-Email: [karlm30@hotmail.com] X-Sender: karlm30@hotmail.com In-Reply-To: From: "Karl M" To: sds@gnu.org, cygwin@cygwin.com Subject: Re: Programatically finding value of "cygdrive" prefix Date: Tue, 16 Aug 2005 16:16:05 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-IsSubscribed: yes >From: Sam Steingold >Subject: Re: Programatically finding value of "cygdrive" prefix >Date: Tue, 16 Aug 2005 17:51:00 -0400 > > > * Igor Pechtchanski [2005-08-16 17:10:25 -0400]: > > > > > > was asking for the actual problem that programmatically accessing the > > cygdrive prefix was supposed to solve. > >I already explained that in >. > >let me try to do it again: > >unix shell scripts and makefiles do not call cygpath. >when they are used under cygwin, they spit out cygwin pathnames >(/cygdrive/c/...) to non-cygwin programs. > >[indeed, if I were using only cygwin-based software, I would have been >OK, but I do not. I prefer the native implementations whenever >possible, so I stick with woe32 versions of CLISP, Mozilla, Emacs and VIM.] > >when a non-cygwin program receives a /cygdrive/c/... pathname, it dies. > >what are my options? > >1. Fix all free software to call cygpath before invoking an editor or a > browser. This does not sound too optimistic. > >2. Fix editors and browsers to handle cygwin pathnames. This requires > an officially published interface, preferably a known registry slot. > 3. Hide these win32 tools (not first on $PATH) and write a wrapper for each. That wrapper can then use cygpath. HTH, ...Karl -- 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/