Xref: utzoo alt.security:1611 alt.bbs:3018 comp.unix.sysv386:651
Path: utzoo!attcan!utgpu!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: alt.security,alt.bbs,comp.unix.sysv386
Subject: Re: Here's how to stop shell escapes from vi
Message-ID: <27477:Sep2320:11:0990@kramden.acf.nyu.edu>
Date: 23 Sep 90 20:11:09 GMT
References: <1990Sep20.153105.28394@naitc.naitc.com> <11285:Sep2022:15:2090@kramden.acf.nyu.edu> <26116@shamash.cdc.com>
Organization: IR
Lines: 15

In article <26116@shamash.cdc.com> jrc%brainiac.uucp@shamash.cdc.com writes:
> You gotta be kidding . What good is vi without : ?  Might as well not
> even use it.  It's like giving your son your car, but not letting
> him put gas in it.  Whoop de doo.       

I said in another article that you should provide macros (not using the
disabled characters) to give the user whatever functions he really
needs. The only fundamental problem is that vi doesn't let you remap the
colon---and pty tr \: \? | pty vi takes care of that.

A more appropriate answer might be: ``You gotta be kidding . What good
is UNIX without sh ? Might as well not even use it.  It's like giving
your son your car, but not letting him put gas in it.  Whoop de doo.''

---Dan