My guess is that Julia doesn't expand the "~" character, as if you were to write \~/Dropbox/Elements/QuickRef/export.txt in a shell.
-erik On Sun, Mar 27, 2016 at 2:46 PM, Lewis Levin <[email protected]> wrote: > Not sure what was wrong with this: > >>> function preparation() >>> >>> run(pipeline(`find -s /Volumes/ll1t/pictures/`, >>> "~/Dropbox/Elements/QuickRef/export.txt")) >>> >>> run(pipeline(`find -s /Volumes/Photos/Pictures/`, >>> "~/Dropbox/Elements/QuickRef/source.txt")) >>> >>> end > > > Error from the shell level was no such file or directory. > > Weird because if I open a shell and run find exactly as shown (with a > redirect of course), it works. > > Same for running within julia with shell escape ;. > > Bunch of oddities in the evolving syntax. If it's not important (probably > isn't) then why not just deprecate the whole thing? No more bugs, no more > documentation. Someone will complain, "I can do shell cmds from Python, > Ruby, ..." to which say, "Sure you can still use those tools and use Julia. > It's all great." > > Not being flip here. It seems like this has changed over the releases; > still seems a bit clumsy (ignoring my own example of user error). It's ok > if it is not a priority. There are lots of things to do. I'll admit it is > a reasonable thing to do, but not if it keeps getting very complicated. > > I'd be happy with spawning a shell and passing a literal and crossing > fingers. No output would come back to Julia but that is ok: mostly likely > use case is to create/modify/delete files. > > Love to know what I did wrong. I was just being lazy and trying to put my > "setup" into the script. Takes 3 secs to do from shell manually. -- Erik Schnetter <[email protected]> http://www.perimeterinstitute.ca/personal/eschnetter/
