From 4686d184967c0c747777c8edcc6b00dc023b8aa9 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Sat, 5 Jun 2021 23:42:03 +0200 Subject: Windows: normalize $COMSPEC * Environment variables are case insensitive on Windows while SciTECO variables are case sensitive. We must therefore make sure that we first unset any $COMSPEC or $ComSpec from the environment before resetting it, thereby fixing its case. * Fixes command execution via on systems where the variable was not called $ComSpec. --- doc/sciteco.1.in | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'doc') diff --git a/doc/sciteco.1.in b/doc/sciteco.1.in index 5441621..6747c5e 100644 --- a/doc/sciteco.1.in +++ b/doc/sciteco.1.in @@ -242,15 +242,19 @@ 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 -.SCITECO_TOPIC "$SHELL" "SHELL" "$ComSpec" "ComSpec" -.BR SHELL " or " ComSpec +.SCITECO_TOPIC "$SHELL" "SHELL" "$COMSPEC" "COMSPEC" +.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 +\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. +Since environment variables are case-insensitive on +DOS-like systems and different spellings exist for \fBCOMSPEC\fP, +the name of the variable is always normalized to all-upper-case +by \*(ST. .TP .SCITECO_TOPIC "$SCITECOCONFIG" "SCITECOCONFIG" .B SCITECOCONFIG -- cgit v1.2.3