Clojurians Log v2
vim
What would be useful questions to ask about Vim/Neovim use in the up-coming Clojure Survey? @neumann suggested questions in the Emacs channel, so I though I'd suggest some questions for the Vim/Neovim community (options for each question are in alphabetical order). Would these be useful (feel free to add / comment in a thread)
## Neovim/Vim
Neovim Distribution
- Nvim AppImage (GitHub release)
- Nvim from source code
- Vim website download
- Vim from source code
- Operating System package (Debian, Arch, Nix, etc.)
- something else
Neovim/Vim version currently used
- Nvim development (pre-release)
- Nvim 11.x
- Nvim 10.x
- Vim 9.x
- Vim 8.x
- something else
Neovim configuration
- AstroNvim
- LazyVim
- Kickstart
- Roll my own vim-script
- Roll my own Lua
- Roll my own Fennel (nfnl)
- something else
Which Clojure REPL plugin do you currently use
- Conjure
- elin
- vim-fireplace
- vim-iced
- vim-slime
- something else
Which Structural Editing plugins do you currently use
- nvim-paredit
- nvim-parinfer
- parpar-nvim (paredit & parnifer)
- vim-style editing
- something else
Which packages for LLM/AI tools do you currently use
- ECA (Editor Code Editor)
- Codeium
- Codex
- Copilot
- something else
You're missing vim-sexp
Vimscript and lua are not mutually exclusive. I reluctantly use lua where I must, called from viml
Thanks I've added vim-sexp. I've rarely used vim itself (only neovim), so any other vim plugin suggestions are welcome. I believe the options are multiple choice, so you can select vimscript and something else. Maybe there is a way to clarify the question to ask what the majority (or preferred) language is for your configuration. Thanks.
vim-sexp works great in neovim, and I feel it is unique amongst the list you provided. Worth giving it a go.
This is what I have as of yesterday evening.
I also have a high-level question about structural editing:
If structural editing means things like paredit then I think that's adequate to cover the main options.
To add context, there is a question that asks about your primary editor. Depending on what you select, the survey will ask you specific questions about that editor.
@jr0cket I'm not so sure about asking about vim/neovim distributions or versions. Perhaps you could elaborate on how that helps the Clojure community.
I find this information useful to know so I can better understand the audience I am writing for. The information would also be very useful to enhance the content on this page https://clojure.org/guides/editors
Yes, we need to make the editors page better for sure. That’s one of the things that prompted this line of questioning .
My concern about version numbers is that it involves research. I have no idea what version of Neovim I’m using. I’d have to figure that out. I’m trying to stick with things people can answer from memory.
However, all the questions are optional. People can skip it.
I'm not sure how relevant neovim or vim version or install method is. Vim plugin development tends to conservative with versions. Neovim less so, but the users embrace that.
@jr0cket To be clear, I think you put together a fantastic set of questions. Thank you!
@nate I’m curious to hear your thoughts too.
> Which packages for LLM/AI tools do you currently use
This is missing an option, of I don't use LLM/AI tools
I think it's optional to fill any
@steven.proctor I like the idea of have a positive statement of "I don't use", so I'll be sure to add it.
Here's the current draft. I'd love any feedback. (Ignore the random line that is highlighted.)
Thanks @jr0cket for your excellent questions!
If you want more AI tools as options, there is also codecompanion.nvim and avante.nvim. They seem quite popular.
It's amazing how many tools have entered this space in the last year.
CopilotChat.nvim is also separate to copilot.vim. Probably not worth it trying to list all the options.
Yeah. I ended up adding a totally different section about AI, and I took it all out of the vim-specific section.
And now the survey is frozen because it's live.
If you haven't taken it yet, I'd encourage you to do so.