In fish shell the operator used to string subsequent commands together is not the same as bash. In bash it is && but in fish it is ; and. This patch makes use of the $SHELL environment variable to check if fish is being used.
I would prefer a method to check which shell vim is currently running in but had no luck and was forced to use the user's preferred shell. At least this will default to using the existing bash syntax and Fish shell users may set the $SHELL environment variable if not set.
I just noticed there is already a similar pull request #126, this is slightly more elegant as it checks for a partial match in the shell environment variable instead of assuming a fixed depth path.
In fish shell the operator used to string subsequent commands together is not the same as bash. In bash it is
&&
but in fish it is; and
. This patch makes use of the$SHELL
environment variable to check if fish is being used.I would prefer a method to check which shell vim is currently running in but had no luck and was forced to use the user's preferred shell. At least this will default to using the existing bash syntax and Fish shell users may set the
$SHELL
environment variable if not set.