-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Goyo on slower computers #32
Comments
Goyo's code is pretty minimal so I don't think you'll get a significant speed boost. So, how slow is it? Did you try disabling other plugins? |
You are right. The slowness wasn't Goyo's fault. I disabled most other plugins and now Goyo mode is snappy. The slowness, however, must have been coming from the interaction of Goyo with some other plugin. I think so because it only manifested itself when all plugins were on and then I entered Goyo mode. (I confess I was sort of becoming a plugin junkie, but now I'm removing the ones that I ended up not using much or whose functionality didn't buy me much more than what vanilla vim already provided). If I find out what interactions were responsible for it, I'll post it here. But I guess I can close this issue now and it's brief existence might be useful for other people who happen to thing Goyo is slowing their vim down, but they should really just disable some of the other plugins they have on. |
Okay, thanks. You might want to check the plugins that update sign column, such as gitgutter, signify, or syntastic. According to my experience, updating sign column usually slows down the rendering of Vim. |
I was wondering what the heaviest part of Goyo's code is. I thought maybe it would be possible to fork it with some removed functionality so as to make it run recently on slower machines (little atom netbooks).
The text was updated successfully, but these errors were encountered: