I wish I could switch to a completely slop-free editor without compromising my workflow too much.
Helix would be a great alternative: Its mappings seem a bit more consistent than Vim’s, also it has Tree-sitter, LSP and fuzzy pickers already built-in. But it lacks some features (digraphs, extensibility, folding – in that order).
I also had a look at Kakoune, which also seems alright, but I don’t like that tabs and splits are delegated to the terminal emulator, a multiplexer or window manager. I respect that decision, but I’d prefer that feature to be built-in.
For now, I’ll stick to Neovim. At least they have a policy that makes LLM users check and sanitise the generated code (https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#ai-assisted-work), although I’d prefer if they’d outright ban it.
More success porting Lilypond/Frescobaldi capabilities over to Neovim: I can now easily do musical transformations on Lilypond notation!
I can transpose passages, double/halve the durations, dot/undot everything, apply a completely new rhythmic pattern, or remove repeated duration indicators or make them explicit again.
This uses the remote plugin feature on Neovim: https://github.com/reillypascal/nvim/tree/main/rplugin/python3
#Neovim #Nvim #Lilypond #Frescobaldi #Python #Composition #ClassicalMusic
Neovim helm users question
I currently have the following installed via lazy:
-- formatting helm charts properly
{
'towolf/vim-helm',
ft = {'helm'},
enabled = true,
},
{
"qvalentin/helm-ls.nvim",
ft = "helm",
opts = {
conceal_templates = {
-- enable the replacement of templates with virtual text of their current values
-- note: for better wrapping support, set `vim.opt.conceallevel = 2`
enabled = false,
},
},
},
I also have tree-sitter installed and I've already done a :TSInstall helm, but for some reason, it's not highlighting my .Values.parameters quite right. See in the screenshot below how it doesn't give me highlights for the period or the word Values.
When I do an :Inspect on the Values, it says:
Syntax
- gotplAction
but that can't be right
What do you think I could be doing wrong?
Not gonna lie, a few years ago when I eared @robinm asking for a built-in plugin manager in #vim / #nvim, I was not convinced.
Why? Because I thought it was already the case. `pack/{opt,start}` has been around for quite a while now and I used #git #submodules to have a portable configuration.
Since then, I've used various plugins manager. They're handy but don't offer much more than the built-in.
And now, back to sugar-coated basics: https://echasnovski.com/blog/2026-03-13-a-guide-to-vim-pack.
I now agree with @robinm.
я наманкипатчил решение :D