impatient.nvim VS nvim-highlite

You could use impatient.nvim or the new vim.loader module if you’re on nightly. Both work really well. I used impatient for a long time and it reduced my startup time by half. I’m using vim.loader now and it reduces it by about the same amount

The 20-30 ms promise depends on your hardware. In my case, vanilla Neovim takes about 18 ms to startup, so a realistic good startup time for my config is around 50-60 ms. Lines of code isn’t a great reference either because you could just lazy load a bunch of plugins and have more LoC but still better startup times. What I would recommend is using lazy.nvim or if you wanna stick with packer, then pairing it with impatient.nvim .

automatically caches all startup code before :h VimEnter or :h BufReadPre (basically what impatient.nvim does)

there is an amazing plugin called impatient.nvim that cache a lot of stuff and make other pluggins go so fast !

Try installing https://github.com/lewis6991/impatient.nvim first.

:lua vim.pretty_print(vim.mpack.decode(vim.mpack.encode({some = { thing = false }}))) used by impatient.nvim

Did you defined your [[ and ]] mappings in that file or just created it? the after directory runs at the end of your config so you can override this kind of settings. Maybe you are using impatient.nvim? From their README:

Are you using impatient.nvim? It caches lua modules. My startuptime with 72 plugins (including it) and zero lazy loading is 600ms.

nivm-highlite boasts ease of configuration, but I haven't tried it yet. It shows only dark themes, but most of the themes support `background=light`. However they are kinda low contrast out of the box.

My plugin and mini.colors can also do it.

tl;dr: export your favorite themes to new formats (e.g. wezterm theme), generate new colorschemes from only a palette of colors, update old colorschemes to automatically include support for new plugins (it sometimes makes them faster too). Repo link

Wow. I just spent like an hour the other day converting colortrans to Lua because I wanted my colorscheme generator to work with all systems, but with this I can just remove built-in support for cterm and suggest mini.color for that purpose.

Mine, nvim-highlite

I do wish there was a builtin way to partially link highlight groups. In my colorscheme I opted for this syntax, which resolves self into the batch of groups being defined recursively unwraps highlight links to fetch the true highlight group being referenced.

Shameless self-plug, but nvim-highlite and all of its inheritors support everything from 8-bit to 256-bt and is written using the Neovim API.

Haven't tried newer color schemes on the block, but I have tried a lot and all of them add 100s of ms to startup time. Eventually settled on a copy of https://github.com/Iron-E/nvim-highlite. Another culprit tends to be all the fancy statusline.

Not to self advertise (regulars here know I do that enough), but my colorscheme is made to work in any range of color. If you don't like it, look under the usage section— all of the colorschemes others have made with it also work without termguicolors.

I'm a little puzzled as to why they'd do that. It's completely possible to use the :colorscheme command.