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 Message-ID: <384D121E.FE0D1074@larocquetrading.com> Date: Tue, 07 Dec 1999 07:56:46 -0600 From: Bryan Headley Organization: LaRocque Trading X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: exec'ing scripts References: <384C0B90 DOT 5F6D71F3 AT larocquetrading DOT com> <19991206165209 DOT D9747 AT cygnus DOT com> <384C36E2 DOT 4576F5D9 AT larocquetrading DOT com> <19991206200935 DOT A11182 AT cygnus DOT com> Content-Type: multipart/mixed; boundary="------------EC95A0761591B716A9635DF2" --------------EC95A0761591B716A9635DF2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Chris Faylor wrote: > On Mon, Dec 06, 1999 at 04:21:22PM -0600, Bryan Headley wrote: > >Chris Faylor wrote: > > > >> 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. > >> > > > >Are you thinking of a tcl script that does an "[shell cal]" not knowing where > >'cal' is? In my case, this is a script that has a, > > > >#! /bin/sh > >exec wish > >[tcl-ish things follow] > > > >The script that it executes was added to the tcl path via, > > > > set auto_path [linsert $auto_path 0 /utils/lib/tkcvs] > > > >So I'm dubious. Plus it's the tcl that ships with cygwin 1 (you might > >assume...) Also, I got B20 to run tkdiff out of the box. So... ??? > > What I'm saying is that "/utils/lib/tkcvs" will be interpreted as > x:\utils\lib\tkcvs where x: is your current drive. > > You may be dubious but tcl/tk does not really support cygwin. What we > have shipped is pretty much what you get when you build tcl/tk natively > on Windows. Well, I finally had to put drive prefixes in all of the paths, and make tkcvs an alias to d:/usr/utils/tkcvs", and things work a lot better. Whot a witch, though. > The alternative is to rewrite tcl/tk to use Windows methods for updating > the screen rather than X methods and no one has ever been ambitious enough > to do this. Probably can avoid that and rewrite the exec internals in the interpreter. Changing how the sucker addresses the screen primitives should yield little (besides, I thought there was a native win32 TK port somewhere. Maybe only for 4.x series...) -- Bryan W. Headley bheadley AT larocquetrading DOT com LaRocque Trading LLC / DA Group (312) 362-4889 (Voice) 440 South LaSalle Street, Suite 740 (312) 362-4924 (Fax) Chicago IL 60605 --------------EC95A0761591B716A9635DF2 Content-Type: text/x-vcard; charset=us-ascii; name="bheadley.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Bryan Headley Content-Disposition: attachment; filename="bheadley.vcf" begin:vcard n:Headley;Bryan x-mozilla-html:TRUE adr:;;;;;; version:2.1 email;internet:bheadley AT larocquetrading DOT com fn:Bryan Headley end:vcard --------------EC95A0761591B716A9635DF2 Content-Type: text/plain; charset=us-ascii -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com --------------EC95A0761591B716A9635DF2--