-
Notifications
You must be signed in to change notification settings - Fork 26
bash: console: command not found #22
Comments
Hmm, that's strange. I think Winpty updated its Cygwin (Babun) name to be I'll check it out and reply back. |
Looks to me like |
But I guess you figured it out with your PR #23, right? Does that solve your issue (may I close it)? |
No, #23 seems to be unrelated. After fixing #23 the install script succeeds, but there is something wrong with the
Perhaps the script could use an explicit path to the console executable, instead of relying on the path? |
@murrayju After merging your PR I updated Winpty to the latest version. So the binary is now I had the following issue: after installing babun-docker from the sources everything worked. But if I removed it completely and installed it from the network (with But I added a notification in the installation to run Coud you try that and let me know? If that doesn't work, try:
|
Still isn't working. Here is what I tried:
Clearly there is something wrong with my |
Hmm, strange, very strange. Could you try the following? Check the permissions of the files in the winpty dir:
Check if your terminal detects
Try to create a link in your home/bin directory:
Try to use the Zsh shell and see if it works with that one:
then restart Babun and run:
|
The solution for:
was simple for me. Stopped using git bash or git-sdk-64 shells, and just used the windows And I tried the |
@agur This is an issue for |
@murrayju did you solve your problem? Should we close this issue? |
I never really solved the problem, but have since moved to using Ubuntu as my primary os... Feel free to close this if you'd like, I probably won't troubleshoot further. |
OK, thanks for replying back @murrayju . And good choice, Ubuntu is also my main OS most of the time. |
I had this same problem, went through your troubleshooting steps, and it finally worked when I switched back to the zsh shell:
Thanks! |
Seems like there is some dependency on something called
console
?The text was updated successfully, but these errors were encountered: