This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (3)
- # alda (1)
- # boot (85)
- # capetown (4)
- # cider (10)
- # clara (16)
- # cljsrn (3)
- # clojars (35)
- # clojure (83)
- # clojure-austin (8)
- # clojure-brasil (4)
- # clojure-canada (16)
- # clojure-greece (2)
- # clojure-ireland (7)
- # clojure-russia (23)
- # clojure-spec (22)
- # clojure-uk (151)
- # clojurescript (97)
- # core-async (10)
- # cursive (1)
- # datascript (7)
- # datomic (21)
- # defnpodcast (13)
- # devcards (3)
- # emacs (4)
- # events (3)
- # hoplon (18)
- # juxt (4)
- # leiningen (7)
- # mount (4)
- # off-topic (2)
- # om (1)
- # onyx (30)
- # planck (6)
- # proton (81)
- # re-frame (3)
- # reagent (9)
- # rum (10)
- # spacemacs (1)
- # specter (6)
- # testing (7)
- # untangled (66)
- # vim (84)
- # yada (23)
anyone have experience with Piggiebacking on boot-cljs-repl? when I run
:Piggieback (adzerk.boot-cljs-repl/repl-env) I get a million NullPointerExceptions printed to my running repl and then it quits
That's what Fireplace should open by default when one tries to eval stuff on cljs buffers
I think we should take example from Emacs users and create Vim-clojure github org with the most important plugins
vim-clojure-static works fairly well though for me. There's a few tweaks that could do with being default, but meh.
I agree. I should have clarified that my thinking was focused on approach over naming.
I guess the best approach is to create the org and then ask several authors if the would like to move few repos there or if we should copy/fork some projects
I can move my clj-async-omni in there. I'm happy for it to get a more consistent name.
Okay. Feel free to copy it, (forking will just make searching harder) or I can do it when I am home later.
that's a neat idea. I've often felt that a bunch of plugins that augment each other like https://github.com/clojure-emacs would be useful for vim.
https://github.com/tpope/vim-fireplace/pull/222 I think we should copy fireplace with this commit.
Hmm, I wonder if there is still some problems with that since tpope has not merged it
Possibly. I've not seen issues myself. It might be that he's busy / not writing so much clojure.
Yeah, he is not writing Clojure afaik but he has been quite active maintaining Fireplace
Problem is that Figwheel is still pretty big. And that's the only way I've managed to get it working.
Hmm, I still have one Figwheel project, I'll check the change with that and ping tpope on the PR
https://github.com/bhauman/lein-figwheel/wiki/Using-the-Figwheel-REPL-within-NRepl maybe I'll try this with one nRepl
I think there's pretty much one import and call within your nrepl to get it to work.
@dominicm: We've been hesitant to try it because it seems a bit crazy - I just keep hoping tpope merges that PR 😕
the fireplace repo said : First, set up cider-nrepl. (If you skip this step, fireplace.vim will make do with eval, which mostly works.)
@juhoteperi: there's an open issue somewhere about a weasel setting for controlling outputs. Related?
I do this a few hours ago,only add [cider/cider-nrepl "0.12.0"] to profiles.clj :user profile can success?@deraen
@juhoteperi: but when I use lein repl command, it's also display the nrepl, is there a way let me test what repl I used?
@juhoteperi: e...well,I mean after I add [cider-nrepl "0.12.0"] to my profiles.clj,then how to open the cider-nrepl
allright,thank you. I have already do this few hours ago,but I feel it's same to use the nrepl without cider-nrepl middleware....
@g1eny0ung: Mainly, you'll notice the difference jumping into dependencies (jar files) and printing out stacktraces
https://twitter.com/JuhoTeperi/status/599954231748075520 but these require cider-nrepl
I bound my omnicomplete in insert mode with <leader>; I have to trigger it to complete