This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-17
Channels
- # aleph (7)
- # announcements (1)
- # aws (12)
- # beginners (118)
- # calva (15)
- # cider (17)
- # clj-kondo (1)
- # cljdoc (11)
- # cljsrn (1)
- # clojure (108)
- # clojure-dev (32)
- # clojure-europe (3)
- # clojure-italy (4)
- # clojure-kc (1)
- # clojure-nl (4)
- # clojure-portugal (1)
- # clojure-spec (29)
- # clojure-uk (69)
- # clojurescript (91)
- # cursive (14)
- # datomic (8)
- # emacs (13)
- # figwheel-main (12)
- # graphql (4)
- # jackdaw (1)
- # jobs (14)
- # lambdaisland (3)
- # luminus (3)
- # nyc (1)
- # off-topic (14)
- # onyx (23)
- # pedestal (8)
- # re-frame (4)
- # reitit (3)
- # shadow-cljs (6)
- # spacemacs (7)
- # specter (2)
- # tools-deps (3)
- # unrepl (4)
- # vim (7)
- # xtdb (10)
@tpope having played with the asyncish omnicomplete on-type, I'm still noticing the delay. I am in ClojureScript where the clojurescript runs on a remote machine (don't ask - corporate envs 😞 ). So I'm probably feeling it more than others would.
I guess the sleep loop means that it still blocks, but you'll see some results at a time until it is completely done? I might try creating a forked cider-nrepl to repo on the JVM where completions have some delay in them.
One option might be to have a #complete
which provides a callback interface. Then I can hook that up into https://github.com/prabirshrestha/asyncomplete.vim quite easily. For now I have a working asyncomplete thing which works reasonably well with some copy-paste.
i think a callback version is a good idea. maybe bolt it on to #omnicomplete
if the method signature doesn't get too convoluted
@dominicm is firing off a callback once for each result sufficient? if it needs all the results at once i don't think it would be sufficient
> Rather than writing your own completion source from scratch you could also suggests other plugin authors to provide a async completion api that works for asyncomplete.vim or any other async autocomplete libraries without taking a dependency on asyncomplete.vim.
I am totally on board for this in theory but they jump from "without taking a dependency" to an example with hard coded references to asyncomplete#