3

On profiling, I found that <SNR>101_parse_screen() is taking above 6 seconds. This problem goes away when I comment out the plugin vim-polyglot. This is most evident for vue files. Not sure if it's a bug, so posting this here.

Not using vim-polyglot is a possible solution, but it seems to work best for me, and don't want to abandon it.

any workarounds?

Will add more details if needed.

  • 1
    Maybe try to temporary remove vim-polyglot, and check with original vue plugin (links in README). Was this issue always present, or started after some update? Also, even if it's not a bug, it's worth asking directly on issue tracker. – grodzik Apr 13 '17 at 8:38
  • 2
    Running :verbose function <SNR>101_parse_screen() would tell you which script that function comes from. – Tommy A Apr 13 '17 at 12:37
  • I agree with grodzik, this sounds like a problem with vim-polyglot. You might have more luck posting it on their issue tracker. – Tumbler41 Apr 13 '17 at 14:33
  • 2
    Ironically, that plugin claims "It won't affect your startup time" in big bold letters :-) – Martin Tournoij Apr 13 '17 at 15:02
3

I did a search on GitHub and Google. From the results, it's pretty reasonable to assume that that function is from vim-css-color, which isn't in vim-polyglot.

In fact it looks like it was removed in 2015 for performance reasons. Are you sure you're using the most recent version of vim-polyglot?

| improve this answer | |
  • I later realized that I was actually using vim-css-color alongside vim-polyglot! that seems to be the culprit. Thanks – nabn Apr 14 '17 at 1:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.