Audrey MP

Also: I haven't bothered with formatting/editing messages (or writing really concise/checked ones; for instance, I made a typo in suppressed) to keep the lines within a character limit, but any...

I'm happy we all dislike the character limit idea. I'll keep doing what I've been doing, then: try to keep my own written messages within 80 to 100 characters or...

If there's a common failure point that you've all seen that I haven't addressed yet, I'd love to hear what it is (either through your own work, or through helping...

After a conversation with @ajd98, I've added in the ability to parse for empty variables within the stdout of the seg log. This is a fairly naive implementation; it relies...

Okay, so I have an implementation of this using regex in Python. It relies on a few things: - Users must run an env command in their runseg (or other...

The only thing I could think of is I wasn't sure whether or not that would catch any defined variables within the executable (IE, if I'm being bad and setting...

I haven't mentioned it, but I share the concern about tying the executable propagator to a shell script. The issue here is that a lot of user problems stem from...

- other scripts/executables/c programs/whatever.

I should mention that I'm not 'tying' it into runseg.sh specifically; it's loading up the executable defined in the configuration settings, and then checking through it. We could put in...

Also, people SHOULD have their runseg.sh error out if certain conditions aren't met, but I think the easier we make it for them to catch errors they haven't thought about...