I just downloaded and installed the Julia 0.7.0 nightly build for Windows. Something seems to have gone wonky with the installation though, since the paths Julia REPL messages output are weird non-existent ones.
julia> @which Markdown.parse("md *md* `md`") parse(markdown::AbstractString) in Markdown at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Markdown\src\Markdown.jl:31
The actual path to the file is
C:\Programs\Julia-0.7.0-DEV\share\julia\stdlib\v0.7\Markdown\src\Markdown.jl. The Julia installation folder
C:\Programs\Julia-0.7.0-DEV\ has been replaced in the output by some non-existent path
C:\cygwin\home\Administrator\... Because the reconstructed path is wrong, commands like
@edit don’t work:
julia> @less Markdown.parse("md *md* `md`") C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Markdown\src\Markdown.jl: No such file or directory
The weird part is that actual calls seem to work and use the correct path, but calls that generate an error have the wrongly constructed path in the output:
julia> Markdown.parse("asdf") asdf julia> Markdown.parse(13) ERROR: MethodError: no method matching parse(::Int64) Closest candidates are: parse(::IO; flavor) at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Markdown\src\parse\parse.jl:94 parse(::IO, ::Markdown.MD; breaking) at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Markdown\src\parse\parse.jl:90 parse(::IO, ::Markdown.MD, ::Markdown.Config; breaking) at C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v0.7\Markdown\src\parse\parse.jl:82 ...
I first assumed this to be a Cygwin issue, or at least a consequence of running Julia under Cygwin, but the same thing happens in the Windows PowerShell command line too. The path shown there is also the
C:\cygwin\home\Administrator\... one, which makes me think it’s a general issue of Julia reconstructing the path wrongly - perhaps the path prefix is something that got set during a cross-compilation that created the nightly build.
Is this a known issue? Or is it something set wrong in my local environment?