Closed vise890 closed 7 years ago
it's probably worth solving #226 asap as well. @ghthor please make sure that i haven't broken anything before merging this.
I don't understand.... wouldn't this make the tests fail if those commands were in /usr/bin?
Yeah, this would break any system where these commands live in /usr/bin
. @vise890 this would break on any *nix I use in my day-to-day.
Is there some reason not to just let your $PATH
handle these, and avoid absolute paths? That appears to be the existing implementation.
Does it really break tho? My understanding/hope was that alias wouldn't care if what you were aliasing didn't actually exist.
Well, it would mean that these aliases don’t work, and since they’re aliasing commands that are needed by the tests, it would stand to follow that the tests would break.
Setting the aliases conditionally, based on OS, would be a more durable move, I think.
I don't think the values from within these aliases make any difference. I think this is a test to assert that the code that adds argument expansion wrapping to these commands will wrap any existing aliases the user had setup. I believe we can just dump these changes if I am correct about this.
That seems reasonable.
right so is this ready to merge?
Yeah, I think for now we should just keep powering forward. I need to setup the travis shit ASAP
On my system (Arch Linux), the commands {mv,rm,sed} live under
/usr/bin
, not under/bin
. So the tests were failing.This commit hard-codes the initial paths to make the tests independent on their real paths.