It looks like the "produced no output" message was introduced in revision 454, way back when. See vm-save.el. It is likely that it didn't fire due to some other bug and, when that was fixed, it started firing again.
In any case, why should this message be blocked?
Cheers, Uday
It looks like the "produced no output" message was introduced in revision
454, way back when. See vm-save.el. It is likely that it didn't fire due
to some other bug and, when that was fixed, it started firing again.
In any case, why should this message be blocked?
Cheers,
Uday