Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Mon, 6 Dec 1999 16:52:09 -0500 To: Bryan Headley Cc: cygwin Subject: Re: exec'ing scripts Message-ID: <19991206165209.D9747@cygnus.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: Bryan Headley , cygwin References: <384C0B90.5F6D71F3@larocquetrading.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <384C0B90.5F6D71F3@larocquetrading.com>; from bheadley@larocquetrading.com on Mon, Dec 06, 1999 at 01:16:32PM -0600 On Mon, Dec 06, 1999 at 01:16:32PM -0600, Bryan Headley wrote: >Is there a good rule of thumb to follow when creating scripts for cygwin >1 to run? If you are talking about executing a tcl script then it is likely that it does not support cygwin paths. That is probably what you're seeing. AFAIK, tcl/tk are close to 100% windows applications with very little understanding of cygwin. They do not understand cygwin's path handling. Sorry. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com