-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Slow startuptime of Ruby files #624
Comments
were you able to profile it? |
I'm pretty sure that you'll have the same issue without vim-plug but with a minimal vimrc like so: filetype plugin indent on
syntax enable You might want to look into |
@junegunn you are right, that also reproduces it, sorry about that! @vheon I have used
|
@alcesleo looks like projectionist is taking the majority of the time there. try to launch vim like: vim --cmd 'profile start profile.log' \
--cmd 'profile func *' \
--cmd 'profile file *' \
-c 'profdel func *'
-c 'profdel file *' \
-c 'qa!' it will give you a more granular profile. |
Using your command I was able to narrow it down to something called @vheon Thank you so much for providing tech support on this misplaced ticket! :) |
I experience very slow start times of Vim with files where the
filetype
isruby
.Ruby files take over 4 seconds to load, and every other filetype I've tried has been quick. The 4s load time happens the first time a Ruby file is loaded, whether Vim is started with a Ruby file, or at the time you switch to one. If you open a second Ruby file, it is also quick.
Example:
$ vim .vimrc
:e Rakefile
(this takes >4s):e something.rb
(this doesn't)I was able to reproduce it with only this in my
vimrc
and all of the plugin folders removed with:PlugClean
(AFAIK, this should mean that no plugins are loaded, only vim-plug code):I haven't been able to dig deeper than this so I apologise if this is not a problem caused by vim-plug. If anyone does have an idea of what could cause this that would be greatly appreciated.
Cheers!
The text was updated successfully, but these errors were encountered: