Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 29 Jun 2000 14:30:14 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: d:/foo to //d/foo to d:\foo to d:/foo Message-ID: <20000629143014.A7594@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <200006291823 DOT OAA19657 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200006291823.OAA19657@envy.delorie.com>; from dj@delorie.com on Thu, Jun 29, 2000 at 02:23:23PM -0400 On Thu, Jun 29, 2000 at 02:23:23PM -0400, DJ Delorie wrote: >Perhaps a cygpath option, like "-/" that means to emit forward slashes >instead of backslashes for Win32 paths? > >Then you could just use $(cygpath -w -/ $HOME) > >But, I don't think the interface between cygwin and non-cygwin >programs is going to get much better as long as we have a mount table. People do mention having some kind of argument control which would allow one to say "if you see something with forward slashes on the command line, translate it to windows format before passing it to 'this specific program'". I wouldn't automatically reject any patch like this but I'm not particularly interested in making this change. To do this correctly, you'd almost need something like the old VMS "CLD" utility which allowed you to precisely define arguments and options. However, something more general would probably be workable. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com