[6737] in SIPB bug reports
Re: pmail / vi on Solaris
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Sun Feb 22 04:13:20 1998
Date: Sun, 22 Feb 1998 04:13:06 -0500 (EST)
To: "Jacob Morzinski" <jmorzins@MIT.EDU>
Cc: bug-sipb@MIT.EDU
In-Reply-To: "[6653] in SIPB bug reports"
From: Salvatore Valente <svalente@MIT.EDU>
Jacob wrote:
when I go into vi, write stuff, and :w it, it think it's
writing it fine, then I :wq, and it says "Fatal error in process"
and sets the text back to what it was before I edited it
Perhaps we should clobber pmail, and force it to stop checking
the return status of editors?
Albert wrote:
a clever way to do this would be to do what "crontab -e" does when it
gets a non-zero exit status: it says
The editor indicates that an error occurred while you were
editing the crontab data - usually a minor typing error.
Edit again, to ensure crontab information is intact (y/n)?
I've decided to implement Jacob's suggestion, since it's easier and
it's sufficient. When composing mail with pmail, after the visual
editor exits, it puts you back in the line editor, even if the visual
editor exists successfully. So, pmail will say "Warning: vi exited
with error status", and then the used can use ~q to abort the message
or ~v to re-edit it.
Jacob, tell your friend to use the Sun dialups. :-)
Have a nice day,
Sal.
