Index: exec.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/exec.n,v
retrieving revision 1.5
diff -c -r1.5 exec.n
*** exec.n	2000/09/07 14:27:47	1.5
--- exec.n	2002/01/28 05:09:03
***************
*** 207,219 ****
  \fBc:/\fR is ignored), and is not equivalent to \fBc:/windows/system\fR,
  which describes a directory on the current computer.  The \fBfile join\fR
  command should be used to concatenate path components.
  .TP
  \fBWindows NT\fR
  .
  When attempting to execute an application, \fBexec\fR first searches for the
! name as it was specified.  Then, in order, \fB.com\fR, \fB.exe\fR, and \fB.bat\fR 
! are appended to the end of the specified name and it searches for
! the longer name.  If a directory name was not specified as part of the
  application name, the following directories are automatically searched in
  order when attempting to locate the application:
  .sp
--- 207,240 ----
  \fBc:/\fR is ignored), and is not equivalent to \fBc:/windows/system\fR,
  which describes a directory on the current computer.  The \fBfile join\fR
  command should be used to concatenate path components.
+ .sp
+ .RS
+ Note that there are two general types of Win32 console applications:
+ .RS
+ 1) CLI -- CommandLine Interface, simple stdio exchange. 'netstat.exe' for
+ example.
+ .br
+ 2) TUI -- Textmode User Interface, any application that accesses the console
+ API for doing such things as cursor movement, setting text color, detecting
+ key presses and mouse movement, etc...  An example would be Win2K's
+ 'telnet.exe'.  These types of applications are not common in a windows
+ environment, but do exist.
+ .RE
+ \fBexec\fR will not work well with TUI applications when a console is not
+ present, as is done when launching applications under wish.  It is desirable
+ to have console applications hidden and detached.  This is a designed-in
+ limitation as \fBexec\fR wants to communicate over pipes.  The Expect
+ extension addresses this issue when communication between a TUI application
+ is desired.
+ .sp
+ .RE
  .TP
  \fBWindows NT\fR
  .
  When attempting to execute an application, \fBexec\fR first searches for the
! name as it was specified.  Then, in order, \fB.com\fR, \fB.exe\fR, \fB.bat\fR,
! and \fB.cmd\fR are appended to the end of the specified name and it searches
! for the longer name.  If a directory name was not specified as part of the
  application name, the following directories are automatically searched in
  order when attempting to locate the application:
  .sp
Index: tclvars.n
===================================================================
RCS file: /cvsroot/tcl/tcl/doc/tclvars.n,v
retrieving revision 1.10
diff -c -r1.10 tclvars.n
*** tclvars.n	2001/11/23 01:29:19	1.10
--- tclvars.n	2002/01/28 05:09:04
***************
*** 43,49 ****
  PATH variable could be exported by the operating system as ``path'',
  ``Path'', ``PaTh'', etc., causing otherwise simple Tcl code to have to
  support many special cases.  All other environment variables inherited by
! Tcl are left unmodified.
  .VE
  .RE
  .RS
--- 43,52 ----
  PATH variable could be exported by the operating system as ``path'',
  ``Path'', ``PaTh'', etc., causing otherwise simple Tcl code to have to
  support many special cases.  All other environment variables inherited by
! Tcl are left unmodified.  Setting an env array variable to blank is the
! same as unsetting it as this is the behavior of the underlying Windows OS.
! It should be noted that relying on an existing and empty environment variable
! won't work on windows and is discoraged for cross-platform usage.
  .VE
  .RE
  .RS