This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-23
Channels
- # announcements (1)
- # architecture (20)
- # babashka (30)
- # beginners (79)
- # calva (27)
- # cider (8)
- # clj-kondo (1)
- # clojure (125)
- # clojure-australia (1)
- # clojure-berlin (4)
- # clojure-europe (62)
- # clojure-france (1)
- # clojure-italy (6)
- # clojure-nl (4)
- # clojure-uk (12)
- # clojuredesign-podcast (5)
- # clojurescript (28)
- # core-async (31)
- # cursive (14)
- # datomic (47)
- # defnpodcast (1)
- # emacs (7)
- # figwheel-main (2)
- # fulcro (10)
- # graalvm (1)
- # graphql (11)
- # jobs-discuss (8)
- # leiningen (2)
- # off-topic (23)
- # rdf (9)
- # re-frame (3)
- # reagent (1)
- # reitit (5)
- # reveal (12)
- # shadow-cljs (12)
- # spacemacs (1)
- # tools-deps (87)
- # vim (22)
- # xtdb (21)
Does anyone use coc.nvim and have problems with it throwing you into random windows when you type fast and it tries to render floating windows?
It's very hard to tell what happens, but I'll be in insert mode, then suddenly scroll to the top of the file, the cursor moves to a different window and whatever I type gets inserted there (even if it's a nonmodifiable window like NERDtree).
ditto here. my gut feeling is that another plugin might be causing that issue. if you have a consistent way to repro the issue, i would recommend bisecting your plugins, removing half and seeing if the issue persists, etc.
I type, it tries to offer suggestions, and as I type, the focus goes, cursor jumps to top of the buffer and I start overwriting my ns
Is that related to the let g:conjure#client#clojure#nrepl#completion#with_context = v:false
setting?
@dharrigan Ah, I'm glad I'm not the only one! I'm trying to make small changes to my init.vim when I have time, to try and find the culprit.
I'm leaning towards it (coc) trying to show additional documentation against the first pop-up
Yes, I think it's the second window, as this only started happening when I started seeing it
@clojurians-slack100 Not sure what that does, but I have it as well in my coc_user_config: ` \ 'disableDiagnostics': 1, `
IIRC coc's diagnostics was clashing with some functionality better provided by something else. I think it's to rather use ALE (with clj-kondo
) for diagnostics, rather than coc. Or it could've been completion 🤷. Just something to try 🙂.
There is some documentation about coc + clj-kondo here: https://github.com/borkdude/clj-kondo/blob/master/doc/editor-integration.md#cocnvim