Josef is really responsive with GR issues... you should open issues when you find anything: https://github.com/jheinen/GR.jl/issues Sometimes it's hard to know if it's a problem with the Plots backend code or with GR itself, but we'll both see the issues. GR is pretty mature, but I agree it's not appropriate for every workflow, and there are still some unfinished todo items.
I think the original problem might crop up when you try to run Julia from multiple processes and you have competing compilation, though I'm sure there's other ways to corrupt your lib directory. On Mon, Sep 12, 2016 at 7:47 AM, Scott Thomas <[email protected]> wrote: > I have not had much luck with the GR backend myself - it looks nice, but > it has no antialiasing on linux yet and I can't close the plot window once > it's open. I think it just needs time to mature some more. > > > On Mon, 12 Sep 2016 at 12:31 DNF <[email protected]> wrote: > >> Thanks. After deleting .julia/lib and restarting julia I get some >> warnings before the prompt shows up: >> >> WARNING: Method definition cgrad(Any, Any) in module PlotUtils at ~ >> /.julia/PlotUtils/src/color_gradients.jl:82 overwritten at ~/.julia/ >> PlotUtils/src/color_gradients.jl:99. >> WARNING: Method definition #cgrad(Array{Any, 1}, PlotUtils.#cgrad, Any, >> Any) in module PlotUtils overwritten. >> WARNING: could not import Base.lastidx into LegacyStrings >> >> >> Plots with PyPlot backend now seems to work. But, I am still having some >> problems with Plots. When I tried using Plots.jl with GR backend, first >> time it worked. If I close the GTKTerm window that GR draws into, just >> nothing happens, and occasionally I get a segfault. >> >> >> On Monday, September 12, 2016 at 1:14:30 PM UTC+2, Scott T wrote: >>> >>> Oh and just to be a little clearer, that's ~/.julia/lib (the .julia >>> folder in your home directory) and not the .../julia/lib folder in >>> Applications. >>> >>> On Monday, 12 September 2016 12:12:08 UTC+1, Scott T wrote: >>>> >>>> Try removing .julia/lib (the precompile cache). I had this same issue >>>> and this appears to have fixed it. >>>> >>>
