As of right now very simple checks are being used in order to check whether or not the process is running, this is done so the pesky error as described in #12 doesn't appear.
As #12 has stated; scenarios can occur where the process list still matches the filter, or maybe it sometimes doesn't match the filter when it should.
I therefore propose an extra configuration property processRegex when if passed, is used instead of the default process check. I don't expect this property to be used often, but for some users with edge cases it could be amazing - #12 woulnd't have been an issue if this was already implemented.
The Readme should also be updated with instructions on setting this up.
As of right now very simple checks are being used in order to check whether or not the process is running, this is done so the pesky error as described in #12 doesn't appear.
As #12 has stated; scenarios can occur where the process list still matches the filter, or maybe it sometimes doesn't match the filter when it should.
I therefore propose an extra configuration property
processRegexwhen if passed, is used instead of the default process check. I don't expect this property to be used often, but for some users with edge cases it could be amazing - #12 woulnd't have been an issue if this was already implemented.The Readme should also be updated with instructions on setting this up.