Is there a channel here for clojure-neovim ? This is the only channel listed under "vim", but neovim feels offtopic here.

I think lots of people in this channel are using neovim, and there is definitely a lot of neovim discussion here.

Given the topic says "all things (neo)vim" and the channel details agree, perhaps we should rename this channel to indicate a broader forum?

@michaelblume created the channel -- any thoughts on a rename?

I do not want to suggest changing channel description with my 2nd msg here, but this is what threw me off: https://imgur.com/a/KLYeo when I searched for "vim", this channel shows title: vim-firepalce description: Tom Pope's fireplace plugin It was not obvious to me how to infer neo-vim from the above.

Probably a good idea to change the channel name. This channel gets quite a bit of discussion about Vim & Neovim for Clojure dev in general, as well as just random Vim talk. It’s where people who use Vim or Neovim and also happen to program in Clojure come to talk about anything even marginally related 🙂

About that, does fireplace work with Neovim?

@niclasnilsson yes

nice

i feel like this channel may as well be called #vim

it's like your one-stop shop for discussing anything related to developing clojure in vim

or neovim

how good is neovim's cloju4re scripting support ? can I use it instead of writing scripts in vimscript ?

@qqq Neovim has an RPC API you can write arbitrary programs against. https://github.com/clojure-vim/neovim-client is a client library for Clojure, for that API. It’s a bit heavyweight though. To use it to create a plugin, there’s still some plumbing you’ve got to do. I would say it’s not a good choice for lightweight scripting due to the learning curve.

I'd also vote for this to have a broader name.

wow, I just got (api/command c ":echo 'Hello Neovim!'") from https://github.com/neovim/neovim/wiki/Installing-Neovim to work -- this is pretty amazing

@qqq it’s fun. That library could definitely be improved, but I think at least that it’s a good example of the type of REPL experience we’d want.

I’ve done some plugins with it, actually recently used it to build an external GUI for embedded Neovim. It worked fine. But I really wish it was easier to get in and make a simple plugin quickly.

I've been trying to think about how I would generate a manifest like other hosts do. Also about how I would load arbitrary libraries/plugins.

Now we're just #vim (to match #emacs as a generic channel).

Yeah @dominicm it needs that level of integration. But I’m not familiar w/ how that side of it works.

Thanks @seancorfield

Woohoo 🙌

@seancorfield: thanks for all your admin work; I have no idea of all the work you do behind the scenes, but it seems every time admin work can make clojurians better, you're always there

NP. Different admins cover different timezones. I'm West Coast US and I'm a night owl so I'm around pretty much all the time the European admins aren't 🙂

@seancorfield I'm curious, what summoned you here?

@qqq asked in #clojure whether there was a general vim channel and I pointed them here, with a suggestion that maybe this channel's focus could be expanded... since I've seen quite a few folks ask about a general vim channel. I'll evaporate soon and no one will even remember I was here 🙂

I'm picturing https://media3.giphy.com/media/PdCgxLYIgrxOU/giphy.gif then you go https://media1.giphy.com/media/xTY7vA2l7qWaI/giphy.gif

@jebberjeb I've been wondering if the solution is a jvm/java plugin loader, where class loaders are used for isolation. It would be very lightweight, and far easier to code in java. The other option is to (load-file) and make clj-embed/tools.deps.alpha available for bootstrapping any dependencies on-demand. Any thoughts on that?

The latter is the least code, but is definitely the slowest. Maybe it would be a good mvp.

@jebberjeb: I'm looking at the diagram in https://github.com/jebberjeb/clojure-socketrepl.nvim Correct me if I'm wrong. There are two jvm processes right? One for running the real clojure repl, and one for running the *.jar. If so, why is there two repls instead of just one?

@qqq dependency conflicts 🙂

@qqq you don't want your vim plugin's version of core-async to mess with your application.

It also means you don't need to add a dependency to your project.

@qqq @dominicm That’s right. It’s definitely not the most efficient approach. But it keeps things isolated.

@jebberjeb I think it's a great solution.

I noticed that clj runs with -Xmx 128M or something, which isn't much, so clojure is quite happy with that.

256M.

@dominicm Yeah, I think using tools.deps.alpha for an MVP might be a good way to go. I know that building w/ Clojure got me farther faster, and it’d be nice to get some burn in time with it on a project like this.

@jebberjeb Have you seen https://github.com/RutledgePaulV/clj-embed ?

@jebberjeb @dominicm: With emacs, it is nice that I can write some elisp code, do a C-x C-e, and test it out. With this approach, where repl = jvm running my clj code editor = jvm running a jar is there a way to define a clojure function, test it out, and have it extend my editor ?

😁 PR welcome.

@dominicm I hadn’t, but that seems like a way around some of the dependency issues we’d face.

I think clj-embed has added a REPL or something, so it would be interesting to expose this somehow.

I'll have a go at a little hack this weekend perhaps. I think this would be quite fun.

With the current neovim-client, It wouldn’t be hard to bolt some Clojure code into your running plugin process at runtime. Off the top of my head, I’m not sure how you’d go about making it callable via Vimscript in such a dynamic way, but I’m sure it’s doable.

But I suppose the plugin could handle that — you could do that w/ Clojure, so it wouldn’t be too bad.

@jebberjeb I'm thinking a convenient command for opening a scratch buffer with some fireplace buffer-local variables set / nrepl connection scoped to it.

This is going to sound silly: is it possible to have neovim, on every key stroke, instead of doing work, pass that keystroke to clojure? [then, I want to have clojure decide what to do with the keystroke / send comamnds back]

This would lose access to all the nice vimscript libs, but would allow clojure, rather than vimscript, to have full control of neovim.

@dominicm can you hook in to every keystroke w/ Vimscript? Because if so you could dish them off to fireplace’s nrepl connection or neovim-client similarly.

I don't think so.