Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!utoday!sean
From: sean@utoday.com (Sean Fulton)
Newsgroups: comp.mail.elm
Subject: Can't invoke /bin/vi (a kludge)
Message-ID: <1991Mar28.065651.20164@utoday.com>
Date: 28 Mar 91 06:56:51 GMT
Organization: UNIX Today!
Lines: 22

Although I haven't had time to really dig in and try to solve the
problem, I've found a quick fix for the problem noted here about ELM
dropping composed messages with ``Can't invoke /bin/vi'' after the
user had successfully written and stored the message.

This is worked for the last 24 hours and is not guaranteed to work on
any system but my own, but it should. I found that putting /bin/vi (or
/usr/bin/vi in our case) in a shell script with ``exit 0'' at the end
and a trap for a clean exit at the top seems to work. I tried this
after noting that users with editors other than vi were not having
problems with ELM.

ELM calls the script, the script calls vi $*, then exits 0, even if vi
bombs. As I said, it seems to work.

Any suggestions for a *real* solution to this problem would be
appreciated.

-- 
Sean Fulton					sean@utoday.com
UNIX Today!					(516) 562-5430
 /* The opinions expressed above are not those of my employer */