diff options
| author | Kevin B Kenny <kennykb@acm.org> | 2003-02-13 22:03:33 (GMT) |
|---|---|---|
| committer | Kevin B Kenny <kennykb@acm.org> | 2003-02-13 22:03:33 (GMT) |
| commit | 5b22ab3651ec3142fdb0850737ffe806327489b8 (patch) | |
| tree | fae3485bd1470f17d9954eb2fafad8d7cbf4a0d0 | |
| parent | a7beeb8e861f0a22b48f42d0725bd6d1c9dc6f73 (diff) | |
| download | tcl-5b22ab3651ec3142fdb0850737ffe806327489b8.zip tcl-5b22ab3651ec3142fdb0850737ffe806327489b8.tar.gz tcl-5b22ab3651ec3142fdb0850737ffe806327489b8.tar.bz2 | |
Added language to describe the handling of the end-of-file character
\u001a embedded in a script file. [Bug 685485]
| -rw-r--r-- | ChangeLog | 6 | ||||
| -rw-r--r-- | doc/tclsh.1 | 16 |
2 files changed, 19 insertions, 3 deletions
@@ -1,3 +1,9 @@ +2003-02-13 Kevin Kenny <kennykb@users.sourceforge.net> + + * doc/tclsh.1: Added language to describe the handling of the + end-of-file character \u001a embedded in a script file. + [Bug 685485] + 2003-02-10 Vince Darley <vincentdarley@users.sourceforge.net> * tests/fileName.test: diff --git a/doc/tclsh.1 b/doc/tclsh.1 index fe55148..bda9e5e 100644 --- a/doc/tclsh.1 +++ b/doc/tclsh.1 @@ -5,7 +5,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: tclsh.1,v 1.7 2002/07/23 18:17:12 jenglish Exp $ +'\" RCS: @(#) $Id: tclsh.1,v 1.8 2003/02/13 22:03:34 kennykb Exp $ '\" .so man.macros .TH tclsh 1 "" Tcl "Tcl Applications" @@ -39,8 +39,18 @@ are made available to the script as variables (see below). Instead of reading commands from standard input \fBtclsh\fR will read Tcl commands from the named file; \fBtclsh\fR will exit when it reaches the end of the file. -There is no automatic evaluation of \fB.tclshrc\fR in this -case, but the script file can always \fBsource\fR it if desired. +.VS 8.4 +The end of the file may be marked either by the physical end of +the medium, or by the character, '\\032' ('\\u001a', control-Z). +If this character is present in the file, the \fBtclsh\fR application +will read text up to but not including the character. An application +that requires this character in the file may safely encode it as +``\\032'', ``\\x1a'', or ``\\u001a''; or may generate it by use of commands +such as \fBformat\fR or \fBbinary\fR. +.VE +There is no automatic evaluation of \fB.tclshrc\fR when the name +of a script file is presented on the \fBtclsh\fR command +line, but the script file can always \fBsource\fR it if desired. .PP If you create a Tcl script in a file whose first line is .CS |