aboutsummaryrefslogtreecommitdiffstats
path: root/lang/tcl-manual/files/patch-tcl8.4.7::html::UserCmd::tclsh.htm
blob: 2af96611916d716be968b6d02a797cac1613924f (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
--- tcl8.4.7/html/UserCmd/tclsh.htm.orig    Tue Jul 27 05:21:39 2004
+++ tcl8.4.7/html/UserCmd/tclsh.htm Thu Nov 18 12:48:14 2004
@@ -4,7 +4,7 @@
 <DL><DD>tclsh - Simple shell containing Tcl interpreter</DL>
 <DD><A HREF="tclsh.htm#M3" NAME="L3">SYNOPSIS</A>
 <DL>
-<DD><B>tclsh</B> ?<I>fileName arg arg ...</I>?
+<DD><B>tclsh8.4</B> ?<I>fileName arg arg ...</I>?
 </DL>
 <DD><A HREF="tclsh.htm#M4" NAME="L4">DESCRIPTION</A>
 <DD><A HREF="tclsh.htm#M5" NAME="L5">SCRIPT FILES</A>
@@ -23,7 +23,7 @@
 <H3><A NAME="M2">NAME</A></H3>
 tclsh - Simple shell containing Tcl interpreter
 <H3><A NAME="M3">SYNOPSIS</A></H3>
-<B>tclsh</B> ?<I>fileName arg arg ...</I>?<BR>
+<B>tclsh8.4</B> ?<I>fileName arg arg ...</I>?<BR>
 <H3><A NAME="M4">DESCRIPTION</A></H3>
 <B>Tclsh</B> is a shell-like application that reads Tcl commands
 from its standard input or from a file and evaluates them.
@@ -56,7 +56,7 @@
 line, but the script file can always <B><A HREF="../TclCmd/source.htm">source</A></B> it if desired.
 <P>
 If you create a Tcl script in a file whose first line is
-<PRE><B>#!/usr/local/bin/tclsh</B></PRE>
+<PRE><B>#!/usr/local/bin/tclsh8.4</B></PRE>
 then you can invoke the script file directly from your shell if
 you mark the file as executable.
 This assumes that <B>tclsh</B> has been installed in the default
@@ -70,7 +70,7 @@
 following three lines:
 <PRE><B>#!/bin/sh
 # the next line restarts using tclsh &#92;
-exec tclsh &quot;$0&quot; &quot;$@&quot;</B></PRE>
+exec tclsh8.4 &quot;$0&quot; &quot;$@&quot;</B></PRE>
 This approach has three advantages over the approach in the previous
 paragraph.  First, the location of the <B>tclsh</B> binary doesn't have
 to be hard-wired into the script:  it can be anywhere in your shell