Bug in vi or ksh?

[dcm at sfsup.UUCP]

In article <2063 at ptsfa.UUCP> jackb at ptsfa.UUCP (Jack Bailey) writes:
>Has anyone noticed this problem:
>
>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.
>
>I think the problem is that the substitution is made using
>eight-bit characters.  I tried this experiment on a monitor
>capable of displaying graphics characters ala ALT-?, and the file
>name is gobbledygreek.
>
>-- 
>J.J.Bailey
>Voice:	415-823-1958
>uucp:	{ihnp4,lll-crg,qantel,pyramid}!ptsfa!jackb

Yep, I had this happen last week.  The folks here booted a new
release of Amdahl UTS and vi bit the dust.  Recompiled vi and all
was well.  So, give that a try.  The freaky thing with this nasty
bug is that it disappears if you make your shell anything other
than K-shell.  

That's the fix.  Now can anyone explain what happened?

				Dave
--

David C. Miller, consultant
Communications Interface Addresses:
    Paperware:  AT&T Information Systems, 190 River Road, Summit, NJ  07901
    Liveware:  (201) 522-6107
    Software:  {allegra,burl,cbosgd,clyde,ihnp4,ulysses}!sfsup!dcm
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On good days life is T.A.N.S.T.A.A.F.L.
On days like today:  T.A.N.S.T.A.A.L.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~