Re: [julia-users] Deprecation warnings using julia on Atom

Colin, Correct, that was a typo. Juno and jewel are working well for me with 0.4 and I wasn't aware M Innes would be switching to Atom. I still haven't been able to get Atom to work well with Julia; I get the same depreciation warnings as you, but I also get some errors that prevent

Re: [julia-users] Deprecation warnings using julia on Atom

I'm not totally sure if this is what you mean by 'compilation in editor', but there is a limitation now that Atom will kill a Julia process that is taking a while to precompile a module. So currently people trigger the precompilation of large modules in the terminal REPL instead. On Fri, Oct 30,

Re: [julia-users] Deprecation warnings using julia on Atom

Have you tried using lightbox? I ran into similar problems with atom, which I prefer due to speed. I could get lightbox to play well with the repl, however and "using jewel". On Tuesday, October 27, 2015 at 10:03:15 PM UTC-4, colint...@gmail.com wrote: > > Done. Precompilation occurred at

Re: [julia-users] Deprecation warnings using julia on Atom

I've not heard of lightbox. Do you mean LightTable? I used to use LightTable with Mike Innes Juno package, but made the switch to Atom because my understanding is that from v0.4 onwards, Mike will be concentrating his efforts there. To be honest, I'm really happy with Atom and the Julia packages.

Re: [julia-users] Deprecation warnings using julia on Atom

Try running "git pull" from within the package directories. Maybe you're on local master but don't have all the commits from remote? What's the most recent commit you see in Atom.jl and CodeTools.jl? -s > On Oct 27, 2015, at 10:03 PM, colintbow...@gmail.com wrote: > > Done. Precompilation

Re: [julia-users] Deprecation warnings using julia on Atom

Here's the latest commit on my local Atom.jl: colin@colin:~/.julia/v0.4/Atom$ git log commit e2d2bd6d4be24acfe72f8e3d91291b424af70512 Merge: 2d78ca1 72a050a Author: Mike J Innes Date: Sat Sep 19 10:13:45 2015 +0100 Merge pull request #9 from ssfrr/depwarn-0_4

Re: [julia-users] Deprecation warnings using julia on Atom

One other potential useful piece of information. I've tried installing packages ink and julia-client both using the Atom package manager, and by following the instructions here: https://github.com/JunoLab/atom-julia-client/tree/master/docs#developer-install but it doesn't make a difference.

Re: [julia-users] Deprecation warnings using julia on Atom

You’re running into another known issue: https://github.com/JuliaLang/julia/issues/12941 Try opening a normal REPL in the terminal and run “using Atom” to trigger the precompilation, then it shouldn’t need to happen when you run from Atom. -s

[julia-users] Deprecation warnings using julia on Atom

Hi all, I'm using Julia v0.4 with the Atom package, on Atom 1.0 with the packages ink, julia-client, and language-julia (and I'm really enjoying this as an IDE solution). I can toggle the Julia console in Atom, and enter code directly into it without any errors or warnings. However, as soon

[julia-users] Deprecation warnings using julia on Atom

You want to be on the master versions: Pkg.checkout("Atom") Pkg.checkout("CodeTools")

Re: [julia-users] Deprecation warnings using julia on Atom

`Pkg.checkout(…)` operates an an already-installed package, so it must be run after `Pkg.add(…)`. -s > On Oct 27, 2015, at 8:31 PM, colintbow...@gmail.com wrote: > > I suppose I could clone the master branch. Is that a bad idea? > > On Wednesday, 28 October 2015 11:30:43 UTC+11,

Re: [julia-users] Deprecation warnings using julia on Atom

Done. Precompilation occurred at the REPL, and I didn't have to do it within Atom. Verified packages are all on Master. Unfortunately, I'm still getting all of the original deprecation warnings when evaluating from the editor in Atom. I'm happy to pursue this further, but am equally happy to