Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!sol.ctr.columbia.edu!emory!gatech!purdue!haven!adm!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.mail.mh
Subject: Re: odd whatnow behaviour
Message-ID: <22594:Feb2801:28:5591@kramden.acf.nyu.edu>
Date: 28 Feb 91 01:28:55 GMT
References: <1991Jan30.203833.16446@cs.utk.edu> <27CBEB10.16195@ics.uci.edu>
Organization: IR
Lines: 16

In article <27CBEB10.16195@ics.uci.edu> jromine@ics.uci.edu (John Romine) writes:
> partain@cs.utk.edu (David L. Partain) writes:
> >We are having occasional annoying behaviour by whatnow that I thought
> >someone might have a fix for...  We suspect that it might in fact be
> >vi returning a wacked out status.
> You are correct.  Complain to your vendor about "vi".  There will be a
> work-around in the next MH patch.

Why not set the editor (prompter-next, or whatever) to a shell script
that always exits 0?

#!/bin/sh
vi ${1+"$@"}
exit 0

---Dan