New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On Windows, Red added to the path, can't be run from another folder on cmd #543
Comments
Some other crashing case (and workaround):
|
This appears to be an issue with the encapper not being able to gracefully handle cases where it is not invoked via a fully specified path. It should have been able to use To do that: rename red.exe to red-exe.exe, and in the same directory as that executable put a red.bat file containing the following line:
Moving the exe out of the way means the batch file will be preferred. The quotes sanitize the path, which uses the cryptic |
Thanks a lot @hostilefork. |
I had this same issue when I was trying to get sublime text to use red as a build system on Ubuntu 15.04. #!/bin/bash
red $@ and called that instead. |
For the Windows batch file, I'd add a
The way I've actually used it is by dropping the executable to my |
Summary
Red can't be run from a different path on Windows.
How to reproduce
Expected behavior
The Red interpreter should run.
Observed behavior
c:>red
PROGRAM ERROR: Invalid encapsulated data.
The text was updated successfully, but these errors were encountered: