Subj : Re: Switch to linux
To   : Andre Robitaille
From : g00r00
Date : Thu Aug 20 2020 12:05 pm

 AR>  g0> I was experimenting with having Mystic automatically add the ./ in Li
 AR>  g0> but I can't remember why I didn't do it.
 AR> 
 AR> 1. Have mis know where it's run from and just make everything without an
 AR> explicit ./ or /mystic path assume the base mystic directory.
 AR> 2. Expanded instructions in the wiki (or an inline help?) about what
 AR> should be happening in those event shell fields.

That's already how it works, but ./ is required to specify current directory
(even if you're in it).

The issue here is that he has an invalid command in the shell command field.
Mystic is properly reporting "this is an invalid command".  In this case its
not misundertanding the shell field, its a misunderstanding of how Linux works.

When I get around to moving the event documentation out of release notes and
onto the Wiki I will note the differences between Windows and Linux to help
out with common mistakes.

--- Mystic BBS v1.12 A46 2020/08/13 (Windows/64)
 * Origin: Sector 7 | Mystic WHQ (1:129/215)

.