Warning messages

[rafaqz]

deomplete-julia: Tagger: WARNING: Task iteration is now deprecated. Use Channels for inter-task communication. A for-loop on a Channel object is terminated by calling c lose on the object.

latest neovim, julia 0.6.0

[oxinabox]

Julia 0.6.0 is not really supported.
I am slowly in the process of moving to a new solution based on https://github.com/JuliaEditorSupport/LanguageServer.jl

Which should be just a matter of making a tiny bit of glue connecting up to https://github.com/autozimu/LanguageClient-neovim

But it has been having issues that I am yet to chase down.

[rafaqz]

Ok that looks like a good solution, hope you work it out!

…

On Wed, Sep 27, 2017 at 12:58 PM, Lyndon White ***@***.***> wrote: Julia 0.6.0 is not really supported. I am slowly in the process of moving to a new solution based on https://github.com/JuliaEditorSupport/LanguageServer.jl Which should be just a matter of making a tiny bit of glue connecting up to https://github.com/autozimu/LanguageClient-neovim But it has been having issues that I am yet to chase down. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACaqeWL00wtowObD7lobmtdedHwKcGLyks5smbnIgaJpZM4PlJEx> .

[oxinabox]

I've been poking it in my off time for like 6 months.
The setup is fairly trivial if you are interested in (attempting) to make it work.

[yelled1]

Obviously, I have 0.6 & this does NOT work.
Do you plan to make it work for 1.x?
Thanks,

[oxinabox]

No.
As stated this is depreciated for julia 0.6+
Including 0.7, 1.0, and 1.x
A language server based solution will work much better.

[yelled1]

Is this what ur referring to?
https://github.com/JuliaEditorSupport/LanguageServer.jl/wiki/Neovim
Seems to be not quite upto far with Juno or even VSCode version :(

[oxinabox]

@yelled1 that is the general notion yes.

If one is really keen one could make a PR to this repo,
and make it work in 0.6+.
I'm not going to because I think (if I had time) my time would be better spent improving and integrating with the language server, than on this old plan.

The fundamental technique I used to create this,
is at best marginally better than the old Juno way (and that is arguable),
and fundamental worse than the Language Server way (used by current VS-code).
Juno is I believe switching to (or has switch to) language server.