3 ms·
It looks very interesting, but the first thing I noticed as a macOS user, is the shell has a built-in command "open" which I expect will conflict with the stand
by gavinmckenzie 5y ago
It looks very interesting, but the first thing I noticed as a macOS user, is the shell has a built-in command "open" which I expect will conflict with the standard macOS command "open" and I haven't found any docs that describe how to deal with this.
- __d 5y agoThis is true of shell built-ins for eg. test too. The solution is to use the full path if you want to use the program, not the shell built-in. In this case, "/usr/bin/open" not "open" will get you the macOS utility. If you get sick of doing that, create a shell alias.