-
Notifications
You must be signed in to change notification settings - Fork 13
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
Use full paths to core Unix commands in functions #23
Comments
Discussions about whether it's smart to alias standard GNU tools (which I assume breaks many a script and program), is that really a robust fix? Different installations might store binaries in different places. Is Not sure if any of these replacement assumptions is more minimal than "vanilla GNU tools are on the PATH". :/ |
I sort of expected/I think that's a reasonable response. I'm used to seeing 3 options: (1) what you suggested with I think it's fairly likely that Are you inclined to take a PR using |
just found another problem related to this. One recommended setting would be create an alias to stat with gstat and then solve the compatibility issue. it seems that this problem is more general and affects OSX users with standard configurations. |
@danielporto, the fact that macOS has a version of |
@reitzig @danielporto OS X doesn't have |
I'm calling it, for now: this won't be fixed. We require GNU-ish tools on the PATH and users to not mess with them. May reconsider if more issues and/or use cases pop up, and a solution that doesn't create more of a mess than solves. I note that they implemented a similar workaround for a few commands in That said, comment jorgebucaran/fisher#79.181039857 seems astute to me: In fish, you can (and probably should) use |
The sdk functions currently assume that the standard Unix commands are first on the path and unaliased (e.g., conf.d/sdk.fish#L45), so if you have something like
rm
aliased to'rm -i'
, runningsdk
will prompt you every time with:This can be fixed by using the full paths to any standard Unix commands (e.g.,
/bin/rm $pipe
instead ofrm $pipe
).The text was updated successfully, but these errors were encountered: