-
Notifications
You must be signed in to change notification settings - Fork 19
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
Warn if bash is not installed #30
Comments
please add additional information to the ticket as specified in the template. In addition MacOS support is limited since I don't have the ability to test code on MacOS. Does nix-shell work if you don't use this plugin? |
i'm seeing the same issue. |
Ah, I forgot that I called |
on commit af6f8a2, no warning message is shown. |
no, wait, the problem is that there is Honestly not sure what to do here. You could detect bash version I suppose, but that sounds like a weird solution?
The shopt call comes from nix itself so no way for us to modify that. |
maybe easiest to mention the problem in README and point to a solution there, so that it's easy to google. |
Could you post the output of I'm thinking of another solution like this right now: if [ -z ${ZSH_NIX_SHELL_BASH_OVERRIDE+x} && $(uname -s) == "Darwin" && $(bash --version | grep -q "3.2") ]; then
echo "A well written warning"
export ZSH_NIX_SHELL_BASH_OVERRIDE="command nix-shell -p bash --command"
fi and then using that override in the shim. |
I can't say it's a good idea to rely on the exact string though -- an OS update could easily changed, this is on MacOS Monterey but I don't know about older versions, etc. |
As far as I understand the bash license changed at some point and this is the latest Version Apple is allowed to ship with MacOS. So I don't think that either the |
Issue description
When bash was not installed, I got this error:
I then ran brew install bash and it fixed things:
I highly recommend that a note be added to the readme for this use case. I have not investigated further why this is happening.
The text was updated successfully, but these errors were encountered: