Vim fireplace does things a little strangely, which is why it happens

Just getting my (neo)vim workflow set up for cljs, and my emacs using coworker demoed how cider runs and shows tests very nicely. Tips on how to configure something similar for the modal editor?

(Not actually using vim-fireplace for now, just jeb's :terminal script)

You'd probably need to find an alternative test output library like humane test output, and use that.

@tomi.hukkalainen_slac and the I guess you’d need to create a mapping to send whatever clojure invokes your tests to that buffer (run-all-tests) or whatever.

@tomi.hukkalainen_slac https://github.com/pjstadig/humane-test-output/blob/master/README.org

Thanks

Hm. Any ideas how to handle multiple :terminal repls? If I read the vimscript correctly, it always tries sending to latest terminal. I can live without doing any other cli work inside neovim, but it would be nifty to be able to somehow send stuff to either serverside or browserside repl

Then again, I'm not sure how useful the clientside repl will be

@tomi.hukkalainen_slac that has been affecting me lately, I’ll open another :term to do something trivial, and it’s a problem. Thinking about it. It’s something I could use myself too.

@tomi.hukkalainen_slac I might take a crack at it. I’m thinking something like a REPLTerm function that takes some id parameter and stores some mapping of id -> term-job-id. Then, some way to toggle between the ids of the active repl terms, and use that to lookup the job id when evaling.

Piggieback scopes by directory, if you're up for something comprehensive

@jebberjeb Ok, looking forward to it!

@tomi.hukkalainen_slac / @jebberjeb have you seen https://github.com/kassio/neoterm ? i've been using it a lot lately, it's awesome

it would probably take some work to integrate it with your clj/cljs toolchain, but the foundation is solid

@dave taking a look now, thanks