Open saladpanda opened 8 years ago
Because for each color it sets up, it runs 20 lines of vimscript to compute the nearest terminal color from an RGB value.
Maybe someone could dig into the optimization of NLKNguyen/papercolor-theme#28 (which more or less related to this project)
Because these colors never change, the 8-bit colors that result from those functions shouldn't change, either; they could probably just be hard-coded.
This is now fixed in my active fork (jsit/vim-tomorrow-theme#3)
awesome that was so fast, thank you very much
I did some profiling with https://github.com/hyiltiz/vim-plugins-profile and found that vim-tomorrow-theme has a surprisingly high impact on vim's startup-time:
while other themes like e.g. Zenburn need way less time:
EDIT: Heres a result with tomasr/molokai (this time measured with bchretien/vim-profiler):
What makes this theme so slow?