This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-08
Channels
- # aws (3)
- # beginners (126)
- # boot (19)
- # cider (31)
- # cljs-dev (324)
- # clojure (96)
- # clojure-boston (2)
- # clojure-denver (9)
- # clojure-dusseldorf (2)
- # clojure-greece (4)
- # clojure-italy (5)
- # clojure-losangeles (1)
- # clojure-spec (18)
- # clojure-uk (59)
- # clojurebridge (1)
- # clojurescript (184)
- # community-development (29)
- # cursive (2)
- # datascript (2)
- # datomic (5)
- # emacs (1)
- # figwheel (6)
- # fulcro (270)
- # hoplon (2)
- # jobs (1)
- # jobs-discuss (1)
- # keyboards (2)
- # leiningen (2)
- # london-clojurians (2)
- # luminus (10)
- # mount (1)
- # off-topic (26)
- # onyx (8)
- # other-languages (1)
- # parinfer (1)
- # protorepl (6)
- # re-frame (23)
- # reagent (61)
- # reitit (5)
- # shadow-cljs (100)
- # spacemacs (3)
- # sql (19)
- # unrepl (90)
- # vim (25)
Is someone running async-clj-omni with recent deoplete? It broke for me due to one of these depoplete changes https://github.com/Shougo/deoplete.nvim/compare/9d048047807b7bfacd7406ebe85acdb1dc019018...master on Cljs project without repl connection (no connection -> error for each completion call)
Those commit messages are useless 😔 I think you've just solved a mystery for us though.
https://github.com/Shougo/deoplete.nvim/commit/1c57338d133a85109dedcc752e4eb384b5bda287 bisected to this commit
not very obvious what in that change would affect this
and gather_candidates specifically, which is what throws the error
Seems like it is enough to just remove this log line: https://github.com/clojure-vim/async-clj-omni/blob/master/pythonx/async_clj_omni/fireplace.py#L80
Probably after the change, this log line is seen by deoplete
@juhoteperi thanks for looking into this change for me (and for fixing it!)
has anyone here tried TimL? it's super old at this point (last commit was 3 years ago), but the idea has always intrigued me
the README mentions that it adds considerable overhead to an already slow host platform, and in 2018 we have good external plugin APIs, so it's probably a non-starter
@dave I looked at it around the same time I discovered that you could compile Vim w/ +mzscheme support. It looks interesting, but the lack of support was a non-starter for me. But I like the idea of compiling to Vimscript in general. Just seems really hard to do well.
Still don’t understand why that didn’t catch on. Native support for scheme as a first class scripting language in Vim has been around for years.
Unfortunately noone is actually running a version of Vim compiled w/ it turned on. But it’s just a flag --enable-mzschemeinterp
.
Yeah, I wish I knew the history of it, why it wasn’t popularized. I actually made a little plugin w/ it too, it was nice.
@dominicm Honestly didn’t really do much w/ it but I was blown away at the time that I could compile support for this ancient feature (+mzscheme) using a modern version of Racket!
Here’a s toy plugin I wrote w/ it. And it worked! https://github.com/jebberjeb/vim-bookmarks-mz