-
Notifications
You must be signed in to change notification settings - Fork 416
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
[linux/fish-shell] Red either fails or runs depending on the way it is called #1547
Comments
I don't know if it's in any way helpful, but other errors I had with this
and
|
Looks like it's an old issue, related to #543. |
I just got this issue on macOS with the fish shell. Should I reopen it? |
@spinningarrow Have you looked at the linked issue #543 ? |
Yes, I did. That one is closed too and I couldn't really find a proper resolution for it (other than creating an alias to red, if I understood correctly). What I'm trying to say is - is this something red can fix from its side; or failing that, provide an error message to the user when it's started incorrectly what the workaround is? I'm also not sure why it works fine with bash but not with fish - what's the difference in the way the binary is invoked? |
I also wonder about it? For now, I solved the issue, by having Red executable in my
|
I'm using fish-shell, so it probably has something to do with the environment. Still, something is fishy.
Bottomline, works under bash, doesn't work under fish when called without specifying the absolute path.
Doesn't happen withred-054
or the automated build that I previously used, commit 7526673.EDIT: Having a red binary in a current folder allows it to launch normally,
red
and./red
both.The text was updated successfully, but these errors were encountered: