scotty

       scotty - A Tcl shell including the Tnm extensions.

SYNOPSIS

       scotty ?fileName arg arg ...?
_________________________________________________________________

DESCRIPTION

       scotty is a Tcl interpreter with extensions to obtain sta­
       tus and configuration information about  TCP/IP  networks.
       After  startup,  scotty  evaluates  the commands stored in
       .scottyrc and .tclshrc in the home directory of the  user.

SCRIPT FILES

       If  scotty  is invoked with arguments then the first argu­
       ment is the name of a script file and any additional argu­
       ments  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/scotty2.1.11
       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 char­
       acters 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
              # the next line restarts using scotty \
              exec scotty2.1.11 "$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 previ­
       ous  approach.   Third,  this  approach  will work even if
       scotty is itself a shell script (this is done on some sys­
       tems  in order to handle multiple architectures or operat­
       ing 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  exe­
       cuted  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
       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 interac­
                         tively  (no  fileName  was specified and
                         standard  input   is   a   terminal-like
                         device), 0 otherwise.

PROMPTS

       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 vari­
       able  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 incom­
       plete commands.

SEE ALSO

       Tnm(n), Tcl(n)

AUTHORS

       Juergen Schoenwaelder <schoenw@cs.utwente.nl>

Tnm                                                     scotty(1)

An undefined database error occurred. SELECT distinct pages.pagepath,pages.pageid FROM pages, page2command WHERE pages.pageid = page2command.pageid AND commandid =