'edquota' failing because vi returns a non-zero code?

[Kyndig]

Anyone know why this is happening?
"Non-zero return from "vi", updated file may contain errors.
Edit again (e) or quit, discarding changes (q)?"

My EDITOR is set to the standard solaris 8 /usr/bin/vi. When I use vi
on any other file and exit, an `echo $#` shows a nice big "0" for a
return code... Why does edquota think there's a non-zero return code
happening here? There is no problem with /tmp either; i can write to
it just fine with vi on any other files. just not this temporary one
created by edquota for some reason.

I found this same question asked several times in the groups, but not
one of them received a response with a solution.

[Casper H.S. Dik]

kyn...@knife-fighting.com (Kyndig) writes:

>Anyone know why this is happening?
>"Non-zero return from "vi", updated file may contain errors.
>Edit again (e) or quit, discarding changes (q)?"

If vi beeps at you because you did something wrong it will later
exit with a non-zero status.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.