This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-24
Channels
- # adventofcode (11)
- # architecture (12)
- # beginners (132)
- # boot (19)
- # cider (26)
- # clojure (69)
- # clojure-dusseldorf (4)
- # clojure-gamedev (1)
- # clojure-italy (46)
- # clojure-nl (4)
- # clojure-serbia (1)
- # clojure-switzerland (2)
- # clojure-uk (91)
- # clojurescript (79)
- # css (4)
- # cursive (2)
- # datomic (16)
- # docs (9)
- # duct (20)
- # editors (94)
- # fulcro (15)
- # graphql (2)
- # hoplon (1)
- # instaparse (7)
- # jobs (3)
- # lein-figwheel (3)
- # leiningen (2)
- # lumo (40)
- # mount (35)
- # off-topic (19)
- # reagent (18)
- # reitit (1)
- # shadow-cljs (123)
- # specter (7)
- # sql (5)
- # test-check (4)
- # tools-deps (38)
- # vim (20)
- # yada (9)
Hey, using vim-fireplace
, I occasionally, accidentally open function docs (the kind one gets with K
) in the preview window. I'd like to do this on purpose, but I haven't been able to figure out how. Anybody here know?
I very rarely use omni-complete, actually... I find ^P sufficient and faster must of the time. But it's possible.
@fatihict I have a compromise I love:
augroup CompletionGroup
autocmd!
autocmd CompleteDone * pclose!
augroup END
It closes the preview after completionlittle question here. with vim-sexp when I create a new pair (f)
and then slurp the next expression in, I end up with two spaces between some-fn and the next expression. any way to prevent this?