-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Executing shell commands no longer works with fish
as shell
#4153
Comments
Damn, this whole "use an interactive shell for running custom commands" feature keeps causing problems. A similar error happens with nushell. A workaround could be to define an alias or function for lazygit that exports SHELL=/bin/bash before calling lazygit. As for a fix, maybe we should look at the |
I'll do the shell export thing for now as a workaround, thanks for the suggestion. I also noticed an occasional command failure when doing a lazygit amend operation that seemed to be similarly shell related – I'll post if it pops up again. These kind of issues do make me consider switching back to |
Thank you, it works great. |
To Reproduce
Run a custom shell command with
fish
set as shell.iTerm2.2025-01-07.at.09.18.34.mp4
The text was updated successfully, but these errors were encountered: