91–100 of 106 posts
Earlier quoted context omitted.
> moving to neovim entails almost zero switching friction As a counter-counterpoint: I tried switching to neovim a couple of weeks ago, and gave up after half a day trying to get syntax highlighting working.
Strange considering neovim has syntax=on by default and it's not even needed in the config. What distro are you using?
Earlier quoted context omitted.
Strange considering neovim has syntax=on by default and it's not even needed in the config. What distro are you using?
I love that the usernames of the two parent comments are so fitting: plugin-baby: (complicated setup?) I see errors worksonmine: WFM No disparagement intended. I'm sure you're both right. My vim config is simple, and neovim handles it well. Including syntax highlighting (some custom). I don't like some of the defaults as much as what shipped with vim, but I know I could configure them out if I cared enough.
Why do you use neovim when it sounds like you’re marginally less happy with it?
I have tried many times to switch to Neovim, but I keep coming back to VS Code. 1. I can't create configs myself. 2. Astro, Lunar ... all break at sometime.
Why not have both? https://github.com/vscode-neovim/vscode-neovim I was using the VSCodeVim plugin, but it kept breaking. I now moved to the Neovim plugin and works great!
I sometimes use Zed but it's subpar in terms of features.
Earlier quoted context omitted.
I'd suggest learning and understanding the vim way of doing things instead of trying to shoehorn the workflow you're used to from VSCode. It's a different world, and it can be really fun to explore but you have to commit. Start small with empty config and no plugins and search the web when ever you want to do things. Yes at first it feels strange and even stupid that you search replace with '%s/oldword/newword/gc'. T…
I don't think the cost versus return ratio is that good for that. I better churn Leetcode questions and get better job
For me it's mastery of my toolbox. Understanding vim pushed me further down the rabbit hole and now my computer works for me. If I help anyone my palms get sweaty as they scroll scroll scroll through the code, but I keep it to myself and remember to breath. Maybe I could do some leetcode (whatever that is) while waiting?
Earlier quoted context omitted.
I love that the usernames of the two parent comments are so fitting: plugin-baby: (complicated setup?) I see errors worksonmine: WFM No disparagement intended. I'm sure you're both right. My vim config is simple, and neovim handles it well. Including syntax highlighting (some custom). I don't like some of the defaults as much as what shipped with vim, but I know I could configure them out if I cared enough.
quesera: also fitting, as you’re happy to go with the flow :-) Why do you use neovim when it sounds like you’re marginally less happy with it?
I don't use neovim, per se.
But sometimes when I run "vi" on one of the various systems I frequent, neovim is what I get.
It doesn't break any of the config I've set explicitly, and doesn't give me wildly unexpected settings aside from that, so I'm good. :)
I just realised that I'm using Neovim despite there are no nvim-specific plugins in my config (CoC covers most of my needs), and I don't use lua. Still is feels like Neovim is more stable and faster than the regular Vim somehow. Plus it has much better defaults.
I use default vim, I believe it was a mistake to fracture the ecosystem with plugins that can only be used with neovim. I have also not found any neovim functionality that sells neovim over vim. Vim is fast enough that I have never even thought about it's speed. With term, termdebug, fzf, ripgrep, and ALE with LSPs and Vim's excellent built in support for auto-completion, tag browsing, and cscope, there's really noth…
It's his project he can do whatever he wants, but I'm planning on using this tool for the rest of my career so I went with the fork. Moving my config to XDG_CONFIG_HOME was a welcome side-effect.
Earlier quoted context omitted.
I don't think the cost versus return ratio is that good for that. I better churn Leetcode questions and get better job
If that's your motivation it could still be useful. Almost every live coding interview I've had so far has a part where I'm explaining the magic tricks I'm performing in vim. I have to remember to slow down and explain my thoughts as I zip through the code or they will just see code moving around the screen. For me it's mastery of my toolbox. Understanding vim pushed me further down the rabbit hole and now my compute…
Part of motivation of the switch was getting a lean environment that doesn't hog resources.
One feature I'm personally excited about is the "undeprecation" of the 'exrc' option, which allows project-specific configuration. Vim (and thus Neovim) has had the 'exrc' option for a long time, which loads any .exrc or .vimrc (or in Neovim's case, .nvimrc) files in the current directory. However, it does this unconditionally, which is obviously a bit of a security concern as a random .vimrc file could contain arbit…
This is basically how direnv and shadowenv work. So if anyone has used those, this is the same idea but it lets you layer on project-specific nvim config without shipping a whole, preconfigured nvim with your projects. Pretty cool!
Congrats to the Neovim team! I know one complaint that people tend to have with nvim is that they can never get to a stable config that they don't need to keep tweaking; I used to be one of those users that kept making changes to their config but I've had a stable config for roughly 6 or so months now and I've been loving neovim and the fact that it's personalised exactly to my liking. So what I'm trying to say is th…