Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
scotty(1)
Edit
PageHistory
Diff
Info
LikePages
scotty !!!scotty NAME SYNOPSIS DESCRIPTION SCRIPT FILES VARIABLES PROMPTS SEE ALSO AUTHORS ---- !!NAME scotty - A Tcl shell including the Tnm extensions. !!SYNOPSIS __scotty__ ?''fileName arg arg ...''? ________________________________________________________________________________________________________________________________________ !!DESCRIPTION __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. !!SCRIPT FILES 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 # the next line restarts using scotty \ 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. !!VARIABLES 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. !!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 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. !!SEE ALSO Tnm(n), Tcl(n), tclsh(1) !!AUTHORS Juergen Schoenwaelder ----
4 pages link to
scotty(1)
:
tkined(1)
nmicmpd(8)
nmtrapd(8)
Man1s
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
