Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Programatically finding value of "cygdrive" prefix Date: Thu, 11 Aug 2005 16:08:30 +0200 Message-ID: <574BF80562AF37419EA4B003C90D756D631392@EXCHANGE1.belgium.fhm.de> From: "Morche Matthias" To: X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j7BE8jdF002939 Have a look at cygstart and Luc Hermitte's cyg-wrapper.sh (http://hermitte.free.fr/cygwin/) -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Sam Steingold ... while we are at it, how do non-cygwin programs supposed to handle this /cygdrive stuff? shell scripts mindlessly transfered from unix to cygwin do not bother to use cygpath before passing pathnames to external programs. native Emacs or vim do not appreciate /cygdrive prefixes. it's easier to tell Emacs how to handle /cygdrive than to fix every elisp Makefile that is being distributed. that brings me to suggest that this "cygdrive" be made available in the registry (which cygwin does not use at all, so, I guess, this is not going anywhere...) ... -- 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/