-
Notifications
You must be signed in to change notification settings - Fork 7
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
Stopped working in zsh #10
Comments
interesting. Do you have a .ok that it's trying to read? |
I got the same. But works if I run it from bash. Ran it on ok-bash root directory so the .ok file is in the repo. |
That commit b3250a9 indeed broke zsh compatibility. Zsh does not accept indirect expansion (but bash does) to go from a variable name to its value. Solved on my laptop both on zsh with the following code L92:L96 Should we fork for a Zsh ? Or create a ok_zsh.sh ? Or simply patch the bash version ? (need to check bash compatibility then). |
I will look into this somewhere in september (because Training: moving to zsh). I think ok-bash should work on zsh as well. Thanks for you patience. |
There were two cases of bad substition, and that was an easy fix. Changed However, there still are some issues. |
People always ask what is "ok." I always refer them to this repo. Unfortunately, it doesn't work out of the box for most mac users because of the need to switch to the zsh branch. I think it should be merged into master if possible. |
The Yes, I agree zsh should work. I'll look into it when I have time (no promises). |
See this PR: #36 |
Zsh support is done. Implementation of autocomplete is another issue. Can this be tested, if you still use it? You will need to checkout the |
Merged. |
Something in commit b3250a9 has added something that causes an issue with zsh.
I'm running Zsh on MacOS
The text was updated successfully, but these errors were encountered: