Replies: 4 comments 6 replies
|
Sorry to hear your frustration. However, this should be addressed in the Discussion section and not in the Issue tracker, as it appears that the problem relies on some plugins rather than on Vim itself, for which I didn't ever have these problems (do you think that I was still using Vim if I would experience all your issues?). Other places for this kind of questions can be Stack Exchange or Reddit. As first suggestion, I propose you to remove all the plugins, and check if the problem persists. If not, add one plugin and retry. Iterate the process until the issue appears again. |
|
To sum it up:
Then I'll use vim. |
|
Just an idea, because you repeatedly emphasize
Are you running Vim within a terminal? And did you test it with a hardware accelerated terminal, e.g. alacritty, ghostty and many others ? |
|
Yes, I always use modal text editors like Vim or Neovim in the terminal. I use the Kitty terminal, and I experience stuttering in Vim that I don't feel when using other high-performance text editors. Of course, I might be too sensitive, but considering the current times, I think this is a reasonable request. I believe this is a need for many people, not just myself. |
Oh, you are the author of neovim/neovim#33736. Are you sure you used stable Neovim version instead of nightly? |
|
I have never used the nightly version. I have always used the latest neovim version from brew. However, the latest neovim version provided by brew was too new and often not stable enough. As a result, I ran into problems and went back to vim. I am currently thinking about it. |
|
What kind of problems do you run into? Is that caused by Nvim or by your plugins? Instead of reporting bug, you decided to falsely accuse Nvim of "indiscriminate updates", while Nvim only releases new features about once a year. FYI, it is Vim that does not "release beta and stable versions separately", while Neovim does have stable and beta version |
|
Maybe I was too sensitive. I thought it would be better to take some time and release a stable version. But my favorite editor is vim/nvim, so I said this. If I offended you, I apologize to all the contributors. |
|
Yes, that was quite offensive. We did take (a lot of!) time to release a stable version, and we have a release process in place for bugfixes for stable releases (we just made another one!) If x.0 releases are too risky for you, that's perfectly fine -- just wait for the first x.1 release then before switching. And if you think you can do it better, by all means do. The world can always use another modal editor. |
What are your plugins? |
Uh oh!
There was an error while loading. Please reload this page.
I used to use neovim. I recently got sick of neovim's indiscriminate updates and switched back to vim. And I completely rewrote the vim configuration file and organized it neatly. I was using it very satisfactorily. However, the problem was that vim's rendering performance was slower than other editors and there were not many plugins worth using among the plugins written in vimscript. And that problem soon caught up with me. Of course, I wrote the configuration file in vim9script instead of vimscript, but most of the plugins were in vimscript and the performance was so slow that the vim editor often stuttered. I was so angry that I thought about rewriting the plugins myself in vim9script, but I didn't have the time. Even if I improved the plugin performance, I couldn't improve the rendering performance. Unless hardware acceleration was supported, the flickering didn't stop when I opened a large file and switched the screen quickly. After comprehensively judging these various situations, I concluded that I would have a hard time using vim. I figured that perhaps my only option was to pick an older, more stable version of neovim and gradually upgrade it. That's why I'm writing this with the small hope that if I share this grumbling with the vim community, something will change.
All reactions