If you can suggest a non-GPL-licensed method of obtaining coreutils, I'd be open to incorporating it somehow. I'm planning on putting together a few packages (where GPL isn't quite as much of an issue) that provide convenience wrappers around busybox-w32 or powershell, but haven't devoted much time to it yet.
A temporary measure you can do is add ENV["PATH"] *= ";" * joinpath (JULIA_HOME,"..","Git","usr","bin") in your juliarc. This will prevent Julia from starting inside Cygwin or MSYS2, which is why I'm reluctant to make this default behavior. (was missing the semicolon in the suggested code snippet first time around, sorry) On Tuesday, January 19, 2016 at 4:15:45 PM UTC-8, Jason Bates wrote: > > Unix shell commands that we happened to be getting from git are no longer >> on Julia's path. This is not temporary. Windows is not unix. If you want to >> use unix shell commands on windows, either download and add your own >> windows posix layer to your path (temporarily in juliarc, not permanently >> where it will break other software), or call powershell which has many >> aliases spelled the same as unix shell commands. > > > This is disappointing. I understand the compatibility issues raised > above, but losing this feature on windows is not a change for the better. > I'm not asking windows to be unix, but access to shell commands of some > sort would be nice. There's very little difference between ;ls and ;dir, > but there is a significant different between ;dir and run(`cmd dir`). > > Just to be sure, do you mean iPython with Python? Or Jupyther a fork of >> it, that works with Julia (and python)? > > > Specifically, I am referring to a Jupyter notebook running an Anaconda > Python 3.5 kernel, versus that same notebook running a Julia 0.4.2 kernel > on Windows 10. With the Python kernel active, the shell magic command %ls > works. With the Julia kernel running, ;ls fails (as does ;dir, or any > other call to a shell command). > > Jason >
