wdawson@crl.com (Willard F. Dawson) writes:
>If I fire up a sub-ksh, and then execute my backgrounded jobs, that ksh
>does not warn me that I have running jobs, nor does it kill my jobs as
>I exit that sub-shell. Why does ksh not perform its "feature" in a
>consistent manner?
Noting the above behaviour, the following code added to my .profile does
the trick (at the expense of having two ksh's loaded while I remain
online):
stty istrip erase '^h'
if [ $0 = "ksh" -o $0 = "-ksh" -o $0 = "-su" -o $0 = "/usr/bin/ksh" ]
then
set -o vi
alias ls="/usr/bin/ls -CFa"
alias f="/usr/bin/finger"
alias j="jobs"
/usr/ucb/stty crt
fi
COUNT=${COUNT:-0}
export COUNT
...
if [ ${COUNT} -eq 0 ]
then
COUNT=1
/usr/bin/ksh
exit
fi
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:09 CDT