When vim plugin will be available? about tern

[snj33v]

+1 on that

[marijnh]

I was planning to start on it next week. But 'available', as in complete, well-tested, and easy to use, that might take a while (I expect ~2 months).

[srusskih]

Greate news! Thanks!

[kuno]

ok, hopefully we can make some contributions to it.

[gilligan]

as for the vim plugin - i took a short glimpse at the tern service and unless i'm mistaken editor plugins are supposed to request completions via http methods ?

I would like to suggest to use a socket connection for interfacing instead. You can have a look at https://github.com/vim-scripts/slimv.vim for a good usage example. The vim-python interface is quite annoying but there is no way around that anyhow.

[marijnh]

Hi Tobias, what is the advantage of a raw socket connection as opposed to HTTP?

[gilligan]

@marijnh performance mostly. Since we are talking about content-assist the delay really needs to be minimal. For that reason i'd say using plain socket communication should be the better approach with minimal overhead. What are you missing in that, that makes you go for http ?

[marijnh]

The overhead for an http request to a local server is tiny (in the order of half a millisecond), so I don't think that argument is significant.

[gilligan]

I guess I would still go for socket communication for simplicity sake - A socket interface might be easier to integrate into a broader range of editors than http communication. Plus you don't really need anything that http has to offer feature wise (?).

You might be right about the performance impact though. Also a matter of how long the actual processing by tern will take in comparison..

[marijnh]

Simplicity and easy integration are exactly the reason I chose HTTP over managing raw sockets.

[gilligan]

well okay never mind then. I still find it odd to use http communication for this but i rest my case then ;)

[kuno]

@marijnh

I saw you just added a vim plugin, thanks ; )

how to use it for now?

[marijnh]

If you source it in your .vimrc, it'll enable Tern-based omni-completion (ctrl-x ctrl-o in insert mode) for JavaScript files.

It is far from finished, though!