| ▲ | sdcfgy 2 hours ago |
| I've used vim since the first time it appeared in Debian repos. I have been told a thousand times that NeoVim is better, more modern and solves many (conveniently never cited) issues. I just ignored it and carried on. Feeling terribly vindicated at this point as it's a feature I use regularly and have no idea that it would be an issue in NeoVim. |
|
| ▲ | kps an hour ago | parent | next [-] |
| I've used vi and nvi and (now) vim, and tried neovim, but :! is broken and “Conform to POSIX vi” is one of their “Non-goals”. |
|
| ▲ | mahboi an hour ago | parent | prev | next [-] |
| I've never used NeoVim because Vim has been good enough. |
|
| ▲ | WesolyKubeczek 2 hours ago | parent | prev | next [-] |
| I used neovim because it felt way faster by default. I think treesitter runs circles around what classic vim is using to highlight syntax. That said, I never used both beyond basics, thus no horror stories either. |
| |
| ▲ | sdcfgy 2 hours ago | parent [-] | | I haven't noticed any performance issues in vim to start with. It was fast on a 75MHz pentium for me. The syntax highlighting, same. No issues. I don't always use that though because I can't be bothered to set up anything much past the basic config. | | |
| ▲ | flohofwoe an hour ago | parent | next [-] | | IIRC vim became really slow with the combination of large source files (thousands of lines of code) and language server plugins (e.g. code completion and live error squiggles). | | |
| ▲ | sdcfgy an hour ago | parent | next [-] | | I had a C program that was a single file 140,000 lines long back then. No issues. | |
| ▲ | WesolyKubeczek an hour ago | parent | prev [-] | | I was using vim-enhanced as red hat-based distro installed it. No customization. No customization of nvim either. I often use vim or nvim on disposable machines, so persistent undo is something very low on my list of things I want. |
| |
| ▲ | everforward an hour ago | parent | prev [-] | | At one point vim lacked asynchronous plugins. If a plugin was running a builder or linter it locked the editor up (from what I recall). That fell apart when people wanted vim to do some more modern IDE kind of things like all the “… on save” stuff (build on save, test, lint, etc). I think LSP support is native in neovim as well. I believe vim merged asynchronous plugin support a while back though, so I’m not sure how different they really are anymore. | | |
| ▲ | sdcfgy an hour ago | parent [-] | | That seems like solving the wrong problem. Just run make from another terminal... | | |
|
|
|
|
| ▲ | na1026 an hour ago | parent | prev | next [-] |
| [dead] |
|
| ▲ | debo_ an hour ago | parent | prev | next [-] |
| *vimdicated |
|
| ▲ | alphabeta3r56 2 hours ago | parent | prev [-] |
| If one really needs an undo in today's day and age, use git. |
| |
| ▲ | leobuskin an hour ago | parent | next [-] | | It’s two different dimensions in this case. VCS doesn’t preserve your local history (in JetBrains’ terms) of changes (and it wasn’t meant to by design) | |
| ▲ | sdcfgy an hour ago | parent | prev | next [-] | | I don't use git. I actually have something still using RCS. | |
| ▲ | an hour ago | parent | prev | next [-] | | [deleted] | |
| ▲ | 0xbadcafebee an hour ago | parent | prev [-] | | Someone didn't read the part about wanting a humane interface |
|
