Is there any BSD-style signal handling built into the player application, or do all the signals default to the default signal action (SIGKILL)?

Mike, could you build in a set of signals to pause the player (INT), re-start the player (HUP)?

One of the few remaining Mk1 owners... #00015

To quote David R. Butenhof "It is always best to avoid using signals in conjunction with threads. When signals and threads meet, beware"[1]

I'd rather not have to handle signals. I'm sure we can come up with another way that would work just as well - how about a named pipe which uses exactly the same commands as the serial port? (Not that I'm volunteering to write it anytime soon!)

[1] Programming with POSIX Threads, David R. Butenhof, Addison Wesley. section 6.6.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

Couldn't someone do something like intercept.c which intercepts the IR codes, but intercept the serial port instead ?

__
Unit serial number 47 (was 330 in the queue)...