I've been using busybox for Windows for a long time and it works well. It has the same behavior as coreutils: one binary with many applets. I avoid conflicts by putting just busybox.exe on my path and running it directly as needed: busybox cat ... or busybox ls .... (More precisely, I have a bb.bat script, but same thing.) I plan to do the same with coreutils -- just put a copy of the EXE in my TOOLS folder, no aliases, no ambiguity.
To do this, I currently have to install coreutils, copy the EXE, and uninstall coreutils.
I would much rather just extract a zip.
Thanks!
I've been using busybox for Windows for a long time and it works well. It has the same behavior as coreutils: one binary with many applets. I avoid conflicts by putting just busybox.exe on my path and running it directly as needed:
busybox cat ...orbusybox ls .... (More precisely, I have a bb.bat script, but same thing.) I plan to do the same with coreutils -- just put a copy of the EXE in my TOOLS folder, no aliases, no ambiguity.To do this, I currently have to install coreutils, copy the EXE, and uninstall coreutils.
I would much rather just extract a zip.
Thanks!