3 ms·
I had this also happen because macos now uses zsh as the default shell and this approach is bash compatible. So you needed additional steps for macos. Not sure
by Folcon 4y ago
I had this also happen because macos now uses zsh as the default shell and this approach is bash compatible.
So you needed additional steps for macos. Not sure if that has been recently resolved?
- alganet 4y agoThere is a fix: https://github.com/jart/zsh/commit/94a4bc14bb2e415ec3d10cf716512bd3e0d99f48 https://github.com/jart/zsh/commit/94a4bc14bb2e415ec3d10cf71... Not sure if it was merged. Her approach is not bash-only, zsh is the odd one out on this one.
- jart 4y agoIt was merged: https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841bc62b06e37134c6e51ea https://github.com/zsh-users/zsh/commit/326d9c203b3980c0f841... We patched fish too! Plus NetBSD sh and FreeBSD sh.
- ok_dad 4y agoIf it's a zsh problem, you need to do something like: bash -c './redbean.com' or whatever your executable is called. ZSH is doing something incorrectly that prevents running these binaries.