Fork me on GitHub
#vim
<
2019-09-16
>
dharrigan07:09:05

oooh, I see neovim 0.4 has been released!

parrot 12
Olical08:09:07

FINALLY! Floating window documentation with Deoplete! 😄

dominicm07:09:45

I wish they would put out change logs :)

dharrigan07:09:43

But a consise, summary would be nicer 🙂

dominicm07:09:44

Exactly where people will look

dharrigan07:09:15

I hope it hits arch soon

Olical08:09:08

Me too, I'll be sudo pacman -Syu most of this week.

Olical08:09:23

I've been holding out for floating windows for a while now.

Olical08:09:05

Although it'll be interesting to see if people overuse them, a regular split is better for most things I think, but stuff like autocomplete and documentation will be great. Virtual text and floating windows are a boon for passive information.

schmee09:09:31

on that note, what is the state of the art for Neovim auto-completion these days?

tvirolai09:09:03

coc.nvim (https://github.com/neoclide/coc.nvim) is gaining ground - it's easy to set up and works great. Deoplete is another alternative

schmee09:09:11

I’ve been using YouCompleteMe for years and haven’t bothered checking anything else out, but these floating windows and virtual text piqued my curiosity 🙂

dominicm09:09:10

I think they make a nicer spot for :echo information

dominicm09:09:37

Eg evaluation results, blame information,

walterl12:09:58

Used YCM for years (the build times were really annoying), then switched to deoplete when I switched to neovim. A few months later I switched to NCM2 and another few months later to coc.nvim

mjw13:09:29

For those using coc.nvim for Clojure, how has it worked out? I use it primarily for TypeScript/JavaScript, but its integration with tsserver is buggy enough that I have <LocalLeader>c mapped to :CocRestart (particularly for TS files)

dave13:09:34

i use coc with https://github.com/snoe/clojure-lsp which is really great, but it's still early days for clojure-lsp, lots of small issues to address with the linting. i think the idea is really solid though. i love my editor being able to lint my clojure code without me needing to have a repl running

mjw13:09:28

Warning for those who’ve upgraded to 0.4 with homebrew: https://github.com/Homebrew/homebrew-core/issues/44324

walterl14:09:06

Also using coc.nvim with clojure-lsp. Looking into configuring the latter with support for schema had me looking into its implementation. It seemed to me like there are some limitations that will be hard to overcome (we'll just have to live with "unknown symbol" errors in macro statements). Still, it delivers the LSP goodness. For the rest there's always integration of NRepl plugins via Fireplace 🙂

Chase15:09:22

I use this: https://github.com/clojure-vim/async-clj-omni with coc.nvim for great autocompletion and floating window docs.

Chase15:09:06

That, with https://github.com/borkdude/clj-kondo for linting. They all seem to work great together for me.

dave15:09:11

i use https://github.com/Olical/conjure , which has a coc plugin that works very nicely and also provides autocompletion and floating window docs it's great to see so many clojure options for vim nowadays!

Olical15:09:36

Wrt autocomplete, I've been on deoplete for years and love it. I found coc too far reaching for my taste with the lsp stuff

☝️ 4
walterl16:09:34

The LSP stuff is exactly why I moved towards the likes of coc 🙂 (didn't like LanguageClient much)

walterl16:09:43

If you're doing IDE-type stuff, why not go all the way?