🚀 go-pugleaf

 > I might have found another variable to my problem with vm-5.31 and
 > timer.  After running timer on its own, I got no errors.  It just
 > returned a number after typing in a number.  If I immediatly re-launch
 > vm after quiting it, I do not get the error "SIGPIPE raised on process
 > timer - closing it." again.  Is this because timer has died for the
 > entire emacs shell or just in the vm shell?

Hmmm.  The timer runs independently of VM, it is the demand for a
timer that causes the timer code to spring into action.  So in
theory any sort of timer allocation should trigger the timer
process to start and the subsequent error.

I'm not sure why you don't get the error the second time around.
The problem might be something inside Emacs that happens the
first time a subprocess is started and doesn't happen again.
Find out if the timer process is running after you re-launch VM.
You can do this with "M-x list-processes".  If the timer code is
running you should see something like

Proc         Status   Buffer         Command
----         ------   ------         -------
timer        Run      (none)         timer