Message-Id: <200808282103.m7SL3plf001547@tigris.pounder.sol.net>
From: cygzw AT trodman DOT com (Tom Rodman)
to: cygwin AT cygwin DOT com
Reply-to: cygwin AT cygwin DOT com
Subject: Re: bash -c '$COMSPEC' # worked sometime b4 cygwin 1.5.24-2
In-reply-to: <48B70CBF.7080606@x-ray.at>
References: <200808241647 DOT m7OGlULH030688 AT tigris DOT pounder DOT sol DOT net> <48B1BA7F DOT 4080300 AT cygwin DOT com> <48B70CBF DOT 7080606 AT x-ray DOT at>
Date: Thu, 28 Aug 2008 16:03:50 -0500
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu 8/28/08 22:38 +0200 Reini Urban wrote:
> Larry Hall (Cygwin) schrieb:
> > There hasn't been any effort to support Windows paths in Cygwin for a long
> > time.  That doesn't mean it wouldn't have worked sometime in the past.  

it worked in cygwin 1.5.19-4

> > It's just that doing so is not a goal of this project.  Use the POSIX form of 
> > the path and will work nicely for you - /cygdrive/d/winnt/system32/cmd.exe.  If
> > you need to use COMSPEC, run it through 'cygpath' to convert it to a POSIX
> > path.
> 
> $ cygstart $COMSPEC
> is an easy alternative.

Thanks, 'cygstart "$COMSPEC"'  - I see, that starts a new console session

--
Will this syntax remain supported?:

  cd "$WINDIR"

Or should I cure my habit of pasting quote protected windows
paths into (interactive bash ) 'cd' commands?

--
thanks,
Tom

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