Fork me on GitHub
#vim
<
2017-08-02
>
hkupty10:08:13

I'll exploit this opportunity in advertise acid once again. Most people from work who use neovim uses acid. I'm not sure what is holding people back from using it here and this would be a valuable feedback so it can be a real (modern and async) alternative to fireplace. Is it just because of the lack of of cljs support?

dominicm11:08:16

That would be a big blocker for me.

zamaterian11:08:55

Me as well, and maybe a little blogpost (like @dominicm, which I found incredible useful) explaining your workflow using acid

juhoteperi11:08:56

The readme doesn't mention if all bindings are configurable, and I can't find the code where they are defined

juhoteperi11:08:30

Looks like (default?) mappings are defined in python command files

juhoteperi11:08:02

Vim doc would be helpful

dominicm13:08:11

Just a total aside, a minor issue I have with fireplace is that it does a special thing for javadoc. But cider-nrepl can already just transparently handle the javadoc case

dominicm13:08:48

Workarounds for older bugs, that pre-date things like cider & such.

hkupty13:08:05

Vim docs and command documentation are top priority for me now. I've also detailed the design and structure a bit more so people can understand better acid without requiring to read the code.

hkupty13:08:01

I've been thinking about writing blog posts about neovim and plugin development. Maybe I should start with acid and clojure development with neovim. Thanks for the tip, @zamaterian!

hkupty13:08:41

I'll try my best to support cljs, but I rarely touch the frontend (my current 'frontend' development is bash/curl/jq)...

hkupty13:08:17

It'll probably be a good idea to have someone who actually uses cljs to help in this front