How do you mean?

> concat all the nses together with a unique prefix to the ns Which nses? Once for each plugin using the neovim-client or once for all? > sent it to the running repl when they started up This has the additional problem of having to star nvim at a folder which already has a repl open..

Once for each plugin using neovim-client. But theoretically you could do once for all. I think the former is better (npm-style deps ftw!). Is that true? I figured you could just hot load your plugin in on first command / on connection / on missing namespace failure.

Maybe we can, but then we're just postponing the load to happen for the first time a command is called, but multiplying it for each separate repl that is open. Also, we end up having several different plugins running on the same repl instance/process, which can lead to a bug in one plugin degrading all other plugins sharing the same process.. Additionally, we're biasing clojure plugins to be used only by clojure developers, since we're requiring a repl to be open... I'm not sure we want that...

True. Maybe it should be possible to infect or to rise from the dead (vimpire?)

😦

for a slow startup plugin to spread to an existing host is a pretty powerful tool I think :thinking_face: I agree we shouldn't require it to be that way. It's a nice thing to support though.

True...

Injecting the clojure code and having an async frontend is a nice alternative to rpc

We can add support to acid, ice and vimpire..

I mentioned vimpire because I was making vampire references, not because I'm excited about it necessarily (just ftr)

Well, it does the trick asynchronously, doesn't it?

Good question, I'm not sure

Maybe we can stick to acid and ice which are those we maintain...

yeah

Wasn't iced moved to clojure-vim?

Not yet https://github.com/mikepjb/ice.nvim

You’re welcome to include it, I’d very much like to have a clojurescript solution where there is no need to npm external dependencies though

it feels very tricky to have a ‘nice’ solution where I’d like a nvim plugin to be a. setup like a regular vim plugin e.g :PlugInstall and b. written in clojure(script)

did you check out nvim-parinfer?

not recently

it's written in clojurescript & is regular plugin

I am looking at it now, I’m loving how well laid out the README is

the installation is relatively simple

I am fairly sure you still need to install the ‘neovim’ npm package though

perhaps this is a missed prerequisite?

It’s not the end of the world, it just bugs me that there is so much setup required to get a plugin to work

You install the node-host plugin and do npm install in it's directory. That's it.

That’s true, I still feel it is so clunky compared to vim-fireplace

agree

I think a small golang shim with vimscript or lua driving it is the only/best way to have something lightweight

s/shim/binary

yes I’m liking that solution more and more

clojure-check is the prior art on that 😉

and fzf.vim too I guess

I was about to say haha

it’s a general pain, I usually recommend atom/protorepl for new developers as a bulletproof way to setup a clojure environment but even that will fail because tools.namespace is missing if you’re on a machine that has never run clojure before

or at least that is my experience!

Didn't have the protorepl issue with TNS. But /shrug

editors are hard 🙂

as are plugins written in external languages!

interesting to see proto-repl is written in coffeescript and clojurescript?!?

nice to see that the package.json deps are gathered without an extra step from the user too

I don’t know the first thing about node-host or <external_language>-hosts in general for neovim but it would be nice if we could include the npm install call

even if it was just to include the ‘neovim’ package

like cider middleware, load up the package you need to communicate with neovim for the language host that you’re using