From b7ce245e859b946deee740bc617f2b997a52e9dd Mon Sep 17 00:00:00 2001 From: Tom Ryder Date: Thu, 27 Dec 2018 00:01:15 +1300 Subject: Two-space sentences in shell comments --- ksh/shrc.d/ksh.sh | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'ksh/shrc.d') diff --git a/ksh/shrc.d/ksh.sh b/ksh/shrc.d/ksh.sh index cc6eeb32..8913b4a1 100644 --- a/ksh/shrc.d/ksh.sh +++ b/ksh/shrc.d/ksh.sh @@ -1,15 +1,15 @@ # If we're running some kind of ksh, we'll need to source its specific -# configuration if it was defined or if we can find it. Bash and Zsh invoke +# configuration if it was defined or if we can find it. Bash and Zsh invoke # their own rc files first, which I've written to then look for ~/.shrc; ksh # does it the other way around. # Unfortunately, this isn't very simple, because KSH_VERSION is set by PDKSH # and derivatives, and in ksh93t+ and above, but not in earlier versions of -# ksh93. To make matters worse, the best way I can find for testing the version +# ksh93. To make matters worse, the best way I can find for testing the version # makes other shells throw tantrums. -# Does the name of our shell have "ksh" in it at all? This is in no way -# guaranteed. It's just a heuristic that e.g. Bash shouldn't pass. +# Does the name of our shell have "ksh" in it at all? This is in no way +# guaranteed. It's just a heuristic that e.g. Bash shouldn't pass. case $0 in *ksh*) ;; *) return ;; @@ -19,7 +19,7 @@ esac # before we proceed ... if [ -z "$KSH_VERSION" ] ; then - # Test whether we have content in the .sh.version variable. Suppress errors + # Test whether we have content in the .sh.version variable. Suppress errors # and run it in a subshell to work around parsing error precedence. # shellcheck disable=SC2234 ( test -n "${.sh.version}" ) 2>/dev/null || return -- cgit v1.2.3