This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-09
Channels
- # aleph (16)
- # bangalore-clj (1)
- # beginners (57)
- # cider (4)
- # clara (1)
- # cljs-dev (25)
- # cljsrn (12)
- # clojure (76)
- # clojure-dusseldorf (2)
- # clojure-italy (41)
- # clojure-russia (4)
- # clojure-spec (3)
- # clojure-uk (122)
- # clojurescript (101)
- # cursive (8)
- # data-science (30)
- # datomic (2)
- # emacs (2)
- # figwheel (10)
- # fulcro (53)
- # garden (5)
- # gorilla (6)
- # hoplon (1)
- # jobs (1)
- # juxt (14)
- # leiningen (12)
- # om (1)
- # om-next (1)
- # onyx (21)
- # pedestal (40)
- # perun (5)
- # portkey (2)
- # re-frame (16)
- # reagent (1)
- # ring-swagger (3)
- # rum (6)
- # shadow-cljs (239)
- # spacemacs (10)
- # specter (9)
- # uncomplicate (2)
- # unrepl (1)
- # vim (13)
- # yada (16)
@dominicm I was curious to your ale & clojure.check linting. I have an active fireplace connection and followed your readme to add both eastwood and kibit as dependencies and installed both ale and clojure-check, but still get the following error:
Error detected while processing function ale#Queue[9]..ale#CallWithCooldown[9]..<SNR>55_ALEQueueImpl[41]..ale#Lint[12]..ale#CallWithCooldown[9]..<SNR>55_ALELintImpl[16]..ale#engine#RunLinters[12].
.<SNR>87_RunLinter[7]..<SNR>87_InvokeChain[1]..ale#engine#ProcessChain[52]..ale#linter#GetCommand[1]..ClojureCheck[1]..ClojureCheckArgs[2]..<SNR>56_ClojureNs: ... (and a few more lines)
. Any idea how I can get it working?^Cool, I am running it with neomake now. Ran into another issue fixed with my minimal vimscript knowledge in this PR: https://github.com/SevereOverfl0w/clojure-check/pull/7/commits/32d68d6295e6e82bb92d4dce60eed2ef4fa797dd 😛
is anyone here using vim-sayid with boot? i'd like to try it out, but it seems like it might rely on a lein plugin
i got an error message asking if i added sayid to my :plugins
, which is a leiningen thing
@dave I've not tried it with boot. I think that message is displayed when the sayid operations are not available, as determined by calling fireplace#op_available
, I don't think there is anything specific in vim-sayid that would make it not work with boot but sayid itself is a lein plugin, isn't it?