Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!uhccux!bt455s10
From: bt455s10@uhccux.uhcc.hawaii.edu (Carl "Art" McIntosh)
Newsgroups: comp.sys.ncr
Subject: Re: ksh
Summary: 8th bit conflict
Message-ID: <6167@uhccux.uhcc.hawaii.edu>
Date: 14 Jan 90 19:44:03 GMT
References: <2039@texbell.swbt.com>
Reply-To: bt455s10@uhccux.UUCP (Carl "Art" McIntosh)
Organization: University of Hawaii
Lines: 30

In article <2039@texbell.swbt.com> jimh@aubsch.UUCP (Jim Hart) writes:
>
>ASPEN is available for the Tower.  I have it, but don't use it, because
>when I spawn a shell from within vi, which is most of the time, I don't
>get ksh, I get Bourne.  I have called ASPEN several times on this, and they
>never get back to me, not even to tell me that it is an NCR problem.

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.

Art Neilson
Bank of Hawaii Tech Support
ARPA: manapua!pilikia!root@trout.nosc.mil
UUCP: {uunet,ucbvax,dcdwest}!ucsd!nosc!manapua!pilikia!root