Subj : Re: Event Timing
To   : McDoob
From : 2twisty
Date : Thu Mar 31 2022 04:20 pm

 Mc> Let ./mis (and ./mutil) take care of Mystic. Don't ask the end user's OS
 Mc> to do it instead. That's a bad habit that programmers should avoid. I
 Mc> would pretend to know.

If Mystic gave me that option, I wouldn't use a workaround.  But if (for some reason) I need to run things with control levels that Mystic doesn't allow, then you could use cron (or any other tool that you want to use to force mystic to execute an event via semaphore)

Sure, it's better to to everything under the single umbrella since it's a lot easier to debug later.  However, I won't adhere to that if I want a specific behavior that I can't otherwise get.

For example, I have already found email reading and maintenance, etc. to be lacking in a few features that my old BBS software from 1993 supported.  So, if I find it annoying enough, I will write something that will give me those functions.  If it's good enough, I'd release it to others if they wanted it. 

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
 * Origin: The Ratrace Losers (21:3/166)

.