-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Current helper binaries are incompatible with fish #264
Comments
For this to work, I’d need to detect which shell is in use. This is possible with an additional command. What is the output of these two commands on your system? echo $SHELL dscl . -read ~/ UserShell | sed 's/UserShell: // That will help me determine which command to use to determine whether Fish is in use. Thanks! |
Same output for both: |
Thanks. I'll see if I can't get this to work later now that I know I can check if (I did a few experiments already, and I'm not sure I can make it work as seamlessly as it currently does with bash/zsh.) |
@marcoluzi Good news, I've got this working. I can now detect if the default user shell is Fish, and if so, a Fish-compatible version of the scripts are generated. Unfortunately, unlike Example usage: Like the other scripts, the variable is only set for the current terminal session! (This doesn't use So you can use Please try out this DEV build and let me know if it works as described: phpmon-dev.zip Note: Fish compatible files are only generated if your default shell ( According to the output you posted above, this should not be an issue, but for others this may be relevant information:
|
@nicoverbruggen |
Fantastic. This is now included in v6.2, which I've just released! Closing this issue now. |
Is there an existing issue for this?
Is this feature request related to a problem?
The fish terminal apparently ignores the
#!/bin/zsh
when i run. pm74
orsource pm74
. It wants to run the script with the fish syntax and thus returns the following error:Describe the solution you'd like to see
Add support for fish shell. Maybe some sort of shell checking when the helper binaries are created.
Additional information or context
No response
The text was updated successfully, but these errors were encountered: