By looking at ~/.julia_history with vi I found the problem: somehow I had 
keyed in at the beginning of a command a character that my vi displays as 
^@, but it is invisible in the REPL. This character at the beginning 
obviously causes REPL do ignore the rest of the statement and just show a 
new prompt "julia>". The command with the in the REPL invisible ^@ at the 
beginning was stored in the command history, and when getting it form the 
history for trying variations of it I only achieved the same again, REPL 
ignored these statements.

When trying to hunt down the problem I upgraded to 0.4, where in the REPL 
the  ^@ is also invisible but causes an error message

ERROR: syntax: invalid character literal ""

Am Mittwoch, 30. September 2015 22:17:29 UTC+2 schrieb Stephan Buchert:
>
> Since today julia refuses to open files for me:
>
> [scb@stride swarm]$ julia -f
>                _
>    _       _ _(_)_     |  A fresh approach to technical computing
>   (_)     | (_) (_)    |  Documentation: http://docs.julialang.org
>    _ _   _| |_  __ _   |  Type "help()" for help.
>   | | | | | | |/ _` |  |
>   | | |_| | | | (_| |  |  Version 0.3.11
>  _/ |\__'_|_|_|\__'_|  |  
> |__/                   |  x86_64-redhat-linux
>
> julia> versioninfo()
> Julia Version 0.3.11
> Platform Info:
>   System: Linux (x86_64-redhat-linux)
>   CPU: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
>   WORD_SIZE: 64
>   BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Haswell)
>   LAPACK: libopenblasp.so.0
>   LIBM: libopenlibm
>   LLVM: libLLVM-3.5.0
>
> julia> f=open("$(homedir())/.juliarc.jl")
>
> julia> f
> ERROR: f not defined
>
> julia> f=Base.open("$(homedir())/.juliarc.jl")
>
> julia> f
> ERROR: f not defined
>
> julia> f=open("doesnotexist")
>
> julia> f
> ERROR: f not defined
>
> julia> f=stat("$(homedir())/.juliarc.jl")
>
> julia> f
> ERROR: f not defined
>
> but
>
> julia> readdir()
> 44-element Array{Union(ASCIIString,UTF8String),1}:
>  "calval"
> ....
>
> Erasing the Fedora julia packages and reinstalling them didn't help, 
> neither does rebooting the system. Otherwise my updated Fedora 22 works 
> fine. Any idea what is going on?
>
> Thanks,
> Stephan
>

Reply via email to