2 Oct
2014
2 Oct
'14
5 p.m.
On Thu, Oct 2, 2014 at 4:39 PM, Simon Peyton Jones
Presumably this is some kind of Windows escape-character problem. But it has worked fine for years, so what is going on?
At a guess, something that was using / is now using \ and getting eaten by the shell. Or quoting that was preventing the \s from being eaten has been lost somewhere. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net