Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 9 Nov 2000 12:57:36 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT sources DOT redhat DOT com
Subject: Re: potential cygwish80 problem
Message-ID: <20001109125736.N1629@redhat.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <27FFF733DAB5D111B5830000F8004B8A1522D6 AT SURDEXNT1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <27FFF733DAB5D111B5830000F8004B8A1522D6@SURDEXNT1>; from karln@surdex.com on Thu, Nov 09, 2000 at 08:52:44AM -0600

On Thu, Nov 09, 2000 at 08:52:44AM -0600, Karl North wrote:
>So the problem appears to be that cygwish80 cannot seem to interpret a
>full (absolute) pathname when it is passed as the first parameter.
>This is the way that the pathname is passed by the "exec" line in my
>script(s).

tcl/tk does not have full understanding of Cygwin paths.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com