🚀 go-pugleaf

>>>>> On 24 Apr 91 15:10:17 GMT, mike-w@cs.aukuni.ac.nz (Mike Williams) said:

>>> On 22 Apr 91 21:11:50 GMT,
>>> "Dan" == Dan_Jacobson@ATT.COM writes:

>>>>> On 21 Apr 91 22:03:38 GMT, kyle@uunet.UU.NET (Kyle Jones) said:

Kyle> Dan_Jacobson@ATT.COM writes:
 > Often my [Amdahl SYS V compiled 18.55] emacs gets stuck on subshell
 > stuff (some kind of SYS V problem, not a VM problem)... so I have to
 > hit ^G, send myself some mail, and then type "g" in VM to hopefully
 > get all the stuff and the nothing-mail I sent myself out of the
 > INBOX.CRASH ... that's when the loop happend ...
 > 
 > Anyway, It [by the way] would be neat if the "g" or some other key
 > would get mail out of the crash box, even if no new mail arrives...

Kyle> It should be doing this already.  (Everyone touch their crash box
Kyle> now and type `g' and see if VM notices it.)

Dan> Actually, I just found probably the most common manifestation of this
Dan> is the state where on disk a message has been appended to INBOX, but
Dan> hitting "g" gives "No new mail."

Mike>   Ouch! I'm not surprised.  In theory, nothing should touch your
Mike> INBOX except VM itself.  That way you never encounter the
Mike> problem of mail being appended to INBOX "on disk" without VM
Mike> knowing about it.

Mike>     If you need to transfer mail from elsewhere, create a new incoming
Mike>   spool file (I use ~/Mail/SPOOL), add it to your vm-spool-files (or
Mike>   MAILPATH), and append to that file instead.

I am trying to say that I have a special situation due to UTS Unix or
something, where I type "g" to get new mail, and vm hangs, so i hit
^G.  [the new message has been appended to INBOX at this point, and
$MAIL is now empty] then i hit "g" and get a `no new mail' message.  i
have to send myself mail & try again until i dont hang [50% of the
time]...

all i ask is that no matter when one hits ^G, there shouldn't be a
state where INBOX can be already appended too [by VM], but the summary
buffer denys it...