🚀 go-pugleaf

In article <12082@tamsun.tamu.edu> (comp.sys.mac.apps), bpb9204@tamsun.tamu.edu (Brent) writes:
> |
> |Tickle 3.1v4 is now available for general consumption.
> | time e.
> 
> I had the version that was available in March and I have a question.
> Is there some variables I need to set with it so that it can find
> the scripts.  For example, when I give it some commands that are
> documented in the tickle manual, it tells me that that command is
> not found.  
> 
> Sorry this is general, but I'm not at my macintosh to check the settings.
> 
> I had the PATH variable set to the directories that contain scripts,
> but this didn't seem to work (the path was set in the tclrc file, I believe).
> 
> Any hints are appreciated  and thanks for your work, Tim.

you can get a list of command with:

	foreach name [info commands] {puts stdout $name} 

Anything not in this list is not available as a command. These commands
are built into tickle and do not need access to any file to be used.

As for commands that are defined in scripts, they will not be available
until you "source script.tcl" them...

tim.


tim endres - time@ice.com  -or-  uupsi!tbomb!time
ICE Engineering, Inc. - Phone (313) 449 8288 - FAX (313) 449-9208
8840 Main Street, Whitmore Lake, MI  48189
USENET - a slow moving self parody... ph