scotty
NAME SYNOPSIS DESCRIPTION SCRIPT FILES VARIABLES PROMPTS SEE ALSO AUTHORS
scotty - A Tcl shell including the Tnm extensions.
scotty ?fileName arg arg ...?
Scotty is a shell-like application that reads Tcl commands from its standard input or from a file and evaluates them similar to tclsh(1). The main difference between tclsh(1) and scotty is that scotty loads the Tnm(n) extension at startup time and that scotty runs in an event-driven mode while tclsh(1) needs a special command to enable the event loop. Scotty evaluates the commands stored in the files .tnmrc and .tclshrc at startup if these files exist in the home directory of the user.
If scotty is invoked with arguments then the first argument is the name of a script file and any additional arguments are made available to the script as variables (see below). Instead of reading commands from standard input scotty will read Tcl commands from the named file; scotty will exit when it reaches the end of the file.
If you create a Tcl script in a file whose first line is
#!/usr/local/bin/scotty3.0.0
then you can invoke the script file directly from your shell if you mark the file as executable. This assumes that scotty has been installed in the default location in /usr/local/bin; if it's installed somewhere else then you'll have to modify the above line to match. Many UNIX systems do not allow the #! line to exceed about 30 characters in length, so be sure that the scotty executable can be accessed with a short file name.
An even better approach is to start your script files with the following three lines:
__#!/bin/sh
exec scotty3.0.0
This approach has three advantages over the approach in the previous paragraph. First, the location of the scotty binary doesn't have to be hard-wired into the script: it can be anywhere in your shell search path. Second, it gets around the 30-character file name limit in the previous approach. Third, this approach will work even if scotty is itself a shell script (this is done on some systems in order to handle multiple architectures or operating systems: the scotty script selects one of several binaries to run). The three lines cause both sh and scotty to process the script, but the exec is only executed by sh. sh processes the script first; it treats the second line as a comment and executes the third line. The exec statement cause the shell to stop processing and instead to start up scotty to reprocess the entire script. When scotty starts up, it treats all three lines as comments, since the backslash at the end of the second line causes the third line to be treated as part of the comment on the second line.
Scotty sets the following Tcl variables:
argc Contains a count of the number of arg arguments (0 if none), not including the name of the script file.
argv Contains a Tcl list whose elements are the arg arguments, in order, or an empty string if there are no arg arguments.
argv0 Contains fileName if it was specified. Otherwise, contains the name by which scotty was invoked.
tcl_interactive
Contains 1 if scotty is running interactively (no fileName was specified and standard input is a terminal-like device), 0 otherwise.
When scotty is invoked interactively it normally prompts for each command with ``% ''. You can change the prompt by setting the variables tcl_prompt1 and tcl_prompt2. If variable tcl_prompt1 exists then it must consist of a Tcl script to output a prompt; instead of outputting a prompt scotty will evaluate the script in tcl_prompt1. The variable tcl_prompt2 is used in a similar way when a newline is typed but the current command isn't yet complete; if tcl_prompt2 isn't set then no prompt is output for incomplete commands.
Tnm(n), Tcl(n), tclsh(1)
Juergen Schoenwaelder
4 pages link to scotty(1):
