this post was submitted on 15 Jun 2024
16 points (94.4% liked)
Neovim
2167 readers
3 users here now
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay so...
I reinstalled Neovim 11 from scratch. ~/.config/nvim/ is empty:
So it seems the crux of the issue is that init.vim isn't parsed properly.
EDIT: but putting "filetype indent off" in ~/config/nvim/init.vim seems to do the trick. Thanks for the hint! This is a lot more complicated than it needs to be ๐
EDIT #2: ":syntax off" doesn't turn off the syntax either. Well, I've had enough. Back to plain old vim...
Oof, that's annoying.
Weird that
:syntax off
doesn't work, from a small test it seems to do the trick for me. But I guess as long as vim works there's no need to replace it ๐Well I've only given Neovim a spin for a few hours, but it's been nothing but an exercise in frustration. Yeah syntax off works in vanilla nvim, but it's replaced by treesitter commands if treesitter is enabled. And treesitter is really, really invasive and aggressive when it comes to highlighting and transparently rewriting what's on the screen.
So basically, without treesitter, it's like vim, only more annoying to configure because init.lua is wildly inconsistent. With treesitter, it breaks my workflow at best (but I suppose I could get used to it) and it silently modifies what I see on the screen vs what I'm actually editing at worst, which is a hard no-no for me.
I think maybe if I configured treesitter from the ground up, I could manage to make it leave my text alone, keep the regex-based syntax highlighting which suits me just fine, and only make treesitter suggest things - which is the only feature I wanted to try Neovim for really. But it's just not worth the incredimazing complication. I've survived just fine without smart hinting from vi for decades, so I can easily do without it.
But hey, thanks man ๐