From 1d5845eed2d9450c84ca046749c73ebde2bdfafb Mon Sep 17 00:00:00 2001
From: Tom Ryder <tom@sanctum.geek.nz>
Date: Wed, 17 Aug 2016 20:15:17 +1200
Subject: Explain ksh.sh a bit more

---
 sh/shrc.d/ksh.sh | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

(limited to 'sh/shrc.d/ksh.sh')

diff --git a/sh/shrc.d/ksh.sh b/sh/shrc.d/ksh.sh
index e95e6d3f..f1245e76 100644
--- a/sh/shrc.d/ksh.sh
+++ b/sh/shrc.d/ksh.sh
@@ -1,5 +1,7 @@
 # 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
+# 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.
 case $KSH_VERSION in
     *'PD KSH '*)
         [ -f "${KSH_ENV:-"$HOME"/.pdkshrc}" ] || return
-- 
cgit v1.2.3