Fork me on GitHub

Hi folks, I'm trying to overhaul this year and I want to get a sense of how valid/outdated this section is: -- Is there an up-to-date, preferred guide that I should be linking to instead? Also, are there other popular vim/neovim plugins that should either try to cover or just link to? Thanks!

nice 2

Maybe I should remove the fireplace-specific page and have a generic Editors page and point people to (and maybe other things)?


For neovim I’d highly recommend This is a guide from the author:

❤️ 2
👍 4
👆 2

I use Neovim and conjure and wrote a little book about it This includes a fennel config

practicalli-johnny10:02:44 covers the basics of many Clojure aware editors, feel free to copy or reference as required


I use conjure with vim ( There's a tutorial (and an interactive school in the editor on how to use)


Thank you, folks! This is excellent information that I will incorporate into the new Clojure Editors page as soon as I've had a !

👍 2

How does this work for vim folks? I'm mostly deferring to the project docs,'s editors page, and but wanted to provide a basic list of options and jumping off points.


@U04V70XH6 for vim-iced it should be vim/neovim. Works for both. Conjure is more specialised for neovim specific features and only works there with much deeper integration and more rich feature set like treesitter etc.


Deferring to the project docs is a good approach for me!


@U7ERLH6JX And vim-fireplace is just vim?


We had this massive split in the vim/nvim universe with nvim going with lua and vim 9+ their own new lang. Things aren’t very compatible nowadays 😅


Well as for fireplace, nvim can also technically run it but in practice no one uses it there I think. Because of the other 2.


And we wonder why setting up an editor environment for Clojure is confusing for newbies... 😕


Yeah it’s a bit of a free for all unfortunately


The way I sort of see it and have made peace with it is if someone is already using vim/emacs, they could might as well be thrown more diverse docs 😅 the confusing array of options is probably inherent here


Yeah... I tend to default to "What editor are you already using?" and if it's one of the four "most popular" for Clojure, just point them at #C099W16KZ #C0744GXCJ #CBE668G4R or #C0DF8R51A 🙂 Otherwise, I try to suggest whichever one of those is closer to what they're already using. I never got the hang of vim, TBH, but I've tried pretty much everything else for Clojure over the years (including Eclipse/CCW and LightTable and a few others).


(I can "get by" with vi if I'm doing something basic on a remote server but that's about it)


Well I’m on the neovim train for about 5 years now and about 3 or so in vim before that. Still stumble on things every once in a while. Nvim using something standard like lua made it much more sane and approachable.


But I think the important bit like you and others mention is not to mix learning clojure along with a new editor too just because others seem to use it. That’s a 🤯

☝️ 2

Maybe we can add a note on those lines too? 😄


Yeah, I'll add a disclaimer at the top of the editors page at some point 🙂


@U7ERLH6JX conjure works just fine without treesitter.

👍 2

I don't use treesitter at all in neovim


Yeah I meant it can use it if enabled and provide more features. It doesn’t work in vim is what I meant more.


To be clear then (mostly for @U04V70XH6's benefit and clear up confusion), neovim with conjure works fine without treesitter enabled. If you do want additional stuff, then yes, you can add in treesitter, but the out-of-the-box experience for clojure developers with the bog-standard install of conjure should get them quite the way there (it says this on the project website that it's technically optional, but highly recommended). Personally, I use conjure with clojure-lsp.

partyparrot 2

Thanks, @U11EL3P9U -- That goes a bit beyond what I feel needs to explain since it's in the project docs.

👍 2

Theree are a few plugins that help (me) if you're interested (for clojure development)


I push up my vimconfig regularly (with mappings and so on). Here are the plugins I use for daily clojure development: .


@U04V70XH6, the disclaimer paragraph looks great! what ive seen also helped newbies to clojure is saying that "there is no best editor for clojure, despite what you may be hearing. its mostly the editor pitch not clojure and all editors have a good clojure story now. no editor strives to be language specific."

👍 2

I still use fireplace. I think it's better than the other plugins still.

Martynas Maciulevičius09:02:20

I use Conjure and my own CIDER test runner mod for Conjure. What I want from Clojure editor is to edit text, evaluate into syntax-highlighted window, be somewhat lightweight and run CIDER tests. I don't want variable explorers, complicated editors and external programs. Maybe I'm used to work with simple data and sometimes you want to see lazy seqs and browse them. But I don't do it. This may not work for most people as I'm used to terminal. Link to my Conjure mod (this has a problem because CIDER can't execute CLJS tests):


> I think it's better than the other plugins still. @U09LZR36F How so?


In summary, it's the plug-in that leverages the most vim features rather than inventing new concepts.


That's good enough for me. That kinda makes sense. Most vim plugins suck now 😛


tpope writes all the best stuff


He's great 😃


@U04V70XH6 You should also mention 'guns/vim-sexp', 'tpope/vim-sexp-mappings-for-regular-people', and 'guns/vim-surround'. These are useful plugins for dealing with s-expressions. There are also plugins for bracket matching, but I don't bother with that. There's also stuff to say about search matching


I could write something for you regarding that


Surely someone's mentioned this already, but Neovim is a fork of Vim, not an extension. I think it's still compatible with Vim at the UI level, but not at the API level.


well its more than just a fork now. has its own lua ecosystem which is largely incompatible with vim. its compatible til vim 8 but not with plugins in vim9script. there are ways around it with neovim mostly to keeps up with the changes in features in vim, actively pulling in patches but chooses to avoid vim9script.


I think forks are generally incompatible 😉


yep, one can expect much more compatibility for vim things in nvim but not the other way round. and its been like that for a while now. things like vim-sexp and lot of tpope things are still the goto ones on nvim, no one wants a lua rewrite 😄

Martynas Maciulevičius16:02:32

> has its own lua ecosystem which is largely incompatible with vim I think I heard that vim9 decided to implement features that nvim has because they started to fear that people will move to nvim. So it's not that vim and nvim aren't compatible -- it's just that vim9 decided to implement more features which aren't backwards compatible.