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 compilation in 
editor. Maybe in time, we'll get it straightened out. I currently think 
it's just a simple communication error between Atom and the REPL but I 
haven't played with them much. 

Thanks!
/R

On Thursday, October 29, 2015 at 6:30:09 PM UTC-4, Colin Bowers wrote:
>
> 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. I think Mike has already got it as friendly and 
> feature-rich as Juno was (as long as you're on the Master branch of the 
> packages, that is). And the deprecation warnings are not a deal-breaker - 
> more a minor inconvenience.
>
> Cheers,
>
> Colin
>
> On 29 October 2015 at 03:45, endowdly <[email protected] <javascript:>> 
> wrote:
>
>> 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, [email protected] 
>> wrote:
>>>
>>> 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 wait it out if 
>>> you're running short on ideas or time.
>>>
>>> Cheers and thanks,
>>>
>>> Colin
>>>
>>> On Wednesday, 28 October 2015 12:24:38 UTC+11, Spencer Russell wrote:
>>>>
>>>> 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
>>>>
>>>>
>>>> On Oct 27, 2015, at 9:09 PM, [email protected] wrote:
>>>>
>>>> Ah... understood. Many thanks.
>>>>
>>>> I'm afraid I'm still not getting the desired result however. After 
>>>> running checkout on "Atom", "CodeTools" and "JuliaParser" I run 
>>>> Pkg.status() and can verify I'm on the master branch for all 3. So I fire 
>>>> up Atom again, try to evaluate in the editor, and get the following error:
>>>>
>>>> INFO: Recompiling stale cache file 
>>>> /home/colin/.julia/lib/v0.4/JuliaParser.ji
>>>> Julia has stopped: 1, null
>>>>
>>>> So I close down Atom, open it again, and try to evaluate in the editor 
>>>> again. This time I get:
>>>>
>>>> INFO: Recompiling stale cache file 
>>>> /home/colin/.julia/lib/v0.4/CodeTools.ji
>>>> Julia has stopped: 1, null
>>>>
>>>> Close down Atom one more time, re-open it and try again. Now I get:
>>>>
>>>> INFO: Recompiling stale cache file /home/colin/.julia/lib/v0.4/Atom.ji
>>>>
>>>> but everything is now working fine. Problem solved? Unfortunately not. 
>>>> I restart Atom again and I'm back to all the deprecation warnings, even 
>>>> though Pkg.status() indicates I'm still on the master branch for Atom, 
>>>> CodeTools, and JuliaParser.
>>>>
>>>> Apologies for the long message. Also, if this is one of those things 
>>>> that will resolve itself over the next couple of weeks as changes from 
>>>> master are pushed to the more stable branches, then I'm happy to ignore 
>>>> the 
>>>> warnings for the time being and not waste anyone's time any further with 
>>>> what is essentially a minor inconvenience.
>>>>
>>>> Cheers,
>>>>
>>>> Colin
>>>>
>>>>
>>>>
>>>>
>>>> On Wednesday, 28 October 2015 11:37:21 UTC+11, Spencer Russell wrote:
>>>>>
>>>>> `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, [email protected] wrote:
>>>>>
>>>>> I suppose I could clone the master branch. Is that a bad idea?
>>>>>
>>>>> On Wednesday, 28 October 2015 11:30:43 UTC+11, [email protected] 
>>>>> wrote:
>>>>>>
>>>>>> Thanks for responding.
>>>>>>
>>>>>> Pkg.checkout("Atom") gives me the error:
>>>>>>
>>>>>> ERROR: Atom is not a git repo
>>>>>>  in checkout at pkg/entry.jl:203
>>>>>>  in anonymous at pkg/dir.jl:31
>>>>>>  in cd at file.jl:22
>>>>>>  in cd at pkg/dir.jl:31
>>>>>>  in checkout at pkg.jl:37
>>>>>>
>>>>>> (I originally did try using Pkg.checkout as per the instructions, but 
>>>>>> got this error, and so went with Pkg.add instead).
>>>>>>
>>>>>> Any thoughts or is this a bug?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Colin
>>>>>>
>>>>>>
>>>>>> On Wednesday, 28 October 2015 11:23:30 UTC+11, Jonathan Malmaud wrote:
>>>>>>>
>>>>>>> You want to be on the master versions:
>>>>>>>
>>>>>>> Pkg.checkout("Atom")
>>>>>>> Pkg.checkout("CodeTools")
>>>>>>>
>>>>>>
>>>>>
>>>>
>

Reply via email to