When fixing the bug in #353 I noticed that even though the checking of the directory and file existence was working, the path was being interpreted within a specific REGEX as a unicode modifier.
This shows up due to Windows path issues. If someone downloads the script and puts it in a directory starting with a p (ex. \pulledpork), perl reads the next character as a modifier. The work around is to copy the script to another directory on Windows, but this needs to be fixed.
When fixing the bug in #353 I noticed that even though the checking of the directory and file existence was working, the path was being interpreted within a specific REGEX as a unicode modifier.
This shows up due to Windows path issues. If someone downloads the script and puts it in a directory starting with a p (ex. \pulledpork), perl reads the next character as a modifier. The work around is to copy the script to another directory on Windows, but this needs to be fixed.