Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!husc6!necntc!custom!boykin
From: boykin@custom.UUCP
Newsgroups: comp.bugs.sys5
Subject: Re: Bug in vi or ksh?
Message-ID: <497@custom.UUCP>
Date: Thu, 5-Feb-87 12:43:46 EST
Article-I.D.: custom.497
Posted: Thu Feb  5 12:43:46 1987
Date-Received: Sat, 7-Feb-87 12:36:24 EST
References: <2063@ptsfa.UUCP>
Distribution: na
Organization: Custom Software Systems; Natick, MA
Lines: 22
Summary: Identification of the problem

In article <2063@ptsfa.UUCP>, jackb@ptsfa.UUCP (Jack Bailey) writes:
> Let's say that during a session of vi, you have your shell set
> to /bin/ksh (from EXINIT, .exrc, or manual setting).  Let's also
> assume you're editing an existing file.  When you perform
> a shell escape with file name substitution using %, the
> program you call says the file does not exist.
> -- 
> J.J.Bailey

The problem is that UNIX VI sets the most significant bit when
the '%' meta-character is expanded.  Csh and sh strip
the data to 7-bit ASCII and hence there is no problem.
Ksh doesn't, hence the lookup fails.

This was one of the things we noticed when we did PC/VI, but
couldn't figure out any good reasons why VI did this.  Among
other reasons why we didn't do this was that DOS's command.com
isn't wild about setting the MSB either.

Joe Boykin
Custom Software Systems
{necntc, frog}!custom!boykin