Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!yale!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!texbell!usm3b2!aubsch!jimh
From: jimh@aubsch.UUCP (Jim Hart)
Newsgroups: comp.sys.ncr
Subject: Aspen ksh
Message-ID: <2136@texbell.swbt.com>
Date: 19 Jan 90 10:01:13 GMT
Organization: NCR Tower Mailing List
Lines: 32
Approved: hack@texbell.swbt.com
Keywords:

Art Neilson writes:
>The reason sh is spawned instead of ksh is the following alias at the
>top of your .env file in your home directory:
>
>alias -x vi='SHELL=/bin/sh vi'
>
>If you read the comments directly above the alias, it reads as follows:
>
>#  Change the vi invocations so /bin/sh is the shell escaped to.
>#This avoids the vi/ksh 8th bit conflict with ":!echo %" like commands.
>
>Note, this info is from the ASPEN ksh on my 386 box at home.  I don't
>have ksh yet for our Tower at work, I am *assuming* that the same
>problem would occur on any box.  If you don't use commands from
>vi like ':!echo %'.  The release notes state "KSH now accepts eight
>bit character sets transparently.  Previous versions used the eighth
>bit internally to keep track of quoting".  I have removed that alias
>from my .env with no problems, I never really tested commands like 
>the above.
>

I have checked my home directory.  There is no .env file.  Sounds like you
may be on the right track, though.  Is there an alias that I could put in
that would fix the problem?  Any other thoughts?

Thanks for responding;
-------------------------------------------------------------
Jim Hart                            uunet!usm3b2!aubsch!jimh
Dept. of Education                  Phone: 207-784-6431
P.O. Box 800, 23 High St.
Auburn, ME     04210
USA