EG and EC use $SHELL and $COMSPEC as the default command interpreters now

 * The default command interpreter will thus be inherited from
   the operating system. In the case of UNIX from the user's
   passwd entry.
   E.g. if bash is used, bash extensions can be used immediately
   if flag 128 is not set in the ED flags.
 * On DOS-like systems there are also alternative interpreters
   (e.g. 4NT, 4OS2) that are configurable now.
 * At least on UNIX with $SHELL it is not guaranteed that
   the interpreter supports the standard command line arguments
   like "-c". If they don't, this will cause problems with EC.
   Since $SHELL is mapped to a Q-Register, it can however
   always be easily customized for SciTECO sessions in the
   user's .teco_ini.

1 files changed, 9 insertions, 0 deletions

diff --git a/doc/sciteco.1.in b/doc/sciteco.1.in
index 468c060..bb7d29b 100644
--- a/doc/sciteco.1.in
+++ b/doc/sciteco.1.in
@@ -208,6 +208,15 @@ Initialization of this variable ensures that the
 \(lq$HOME\(rq Q-Register is available even on Windows
 and the home directory can always be re-configured.
 .TP
+.BR SHELL " or " COMSPEC
+Path of the command interpreter used by \fBEG\fP and \fBEC\fP
+commands if UNIX98 shell emulation is \fIdisabled\fP.
+\fBSHELL\fP is used on UNIX-like systems, while \fBCOMSPEC\fP
+is used on DOS-like systems (like Windows).
+Both variables are usually already set in the process environment
+but are initialized to \(lq/bin/sh\(rq or \(lqcmd.exe\(rq
+should they nevertheless be unset.
+.TP
 .B SCITECOCONFIG
 Path where \*(ST looks for configuration files.
 For instance, this is the path of the default profile.