Sebastian Pfitzner

Do you still have `node` on your path, and if you do, can you try removing that was well?

Did anyone give `apx` a try?

Are you using Julia 0.6.2? If not, please do so.

IIRC this warning tries to figure out when a binding *changes* type, so e.g. was a `Tuple{int64,Int64}` but then got assigned `nothing`. In your particular case the warning seems kinda...

> Maybe a better message is `Warning: is changed to Nothing` or something like that. Agreed. > Also, if I'm not mistaken, the compiler is much better at optimizing for...

It's not always trivial to find the correct line info, but yes, probably a bug.

You can specify the `modules` kwarg to get only warnings in the specified modules (as per the docstring).

Hard to tell what's going on here, but it very likely isn't related to Juno.

Probably because you're actually getting a different "environment" in Juno vs the REPL. And this happens because Juno already loads a bunch of packages, so things break if your Manifest...

This is going to happen whenever you do a `pkg> activate Foo` where the environment Foo specifies a version of one of Atom.jl's dependencies different from the one in Atom's...