i was under the impression that conjure supports socket repl. is it not the case?
prepl isn't powerful enough for providing good tools, I was reinventing a bad nREPL. I don't have enough time to do that really, I'd rather spend time making things that work well and have good UX for people that need it, so I built in nREPL instead and ended up being able to delete 50% of my code while ending up with something more powerful and stable.
And it wasn't socket REPL, it was specifically prepl because socket REPL doesn't distinguish between what's a result, stdout or stderr. I will add support for Clojure over prepl in Conjure again one day (probably) but it'll be extremely weak in comparison to what you can do with nREPL.
I spent a good two years trying to be prepl only, I still don't regret giving up.
I've written maaaany times on my blog and spoken in a few talks about how prepl is good for some simpler things, but for interactive editor tooling with lots of async evaluations, it's just not good enough.
i see. it all makes sense now. thank you very much for all the effort you put into Conjure! as a proud member of Clojurist Together, i hope youβre taking advantage of it and being compensated for your effort and time. π
I'm a member too π I'm not benefiting from it right now but that's totally fine, I have my own personal wonderful independent sponsors on GitHub that fuel my coffee habit and Conjure work on the weekends π Actually I do benefit from CT indirectly from the work on CIDER etc, that helps me out MASSIVELY.
an earlier version supported prepl, but the latest utilizes nrepl
seeing the https://clojurians.slack.com/archives/C06MAR553/p1610022945015300, I was wondering, is this magic available to us via any of the available vim clojure plugins?
it works with coc-nvim
I have the following mapping (which I took from cocβs readme I think)
nmap <leader>qf <Plug>(coc-fix-current)
It also works as a code action in the nvim lsp