startuptime.vim VS CosmicNvim

You could use https://github.com/tweekmonster/startuptime.vim. Then you can run :StartupTime -- big-file.txt

tweekmonster/startuptime.vim is inaccurate. I think it doesn't take Lua into account. Don't use this plugin.

I recently had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for traditional Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Vim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine).

Lastly, I also had a look at startup performance. Using the startuptime plugin both moonfly & nightfly were taking around 4.5ms to load on my quad-core Linux desktop (not too bad for Vimscript-based colorschemes). Some profiling did indicate that clearing highlights and resetting syntax are actually quite expensive. We really don't need to do either when loading a colorscheme at Neovim start time; it is only really needed when changing colorschemes within an existing edit session. Putting in a simple guard results in moonfly & nightfly now taking only 2.5ms to startup (on my machine). That is quite similar to some of the nice new Lua-based Neovim colorschemes now available. A win, albeit a small one.

Using the :StartupTime provided by https://github.com/tweekmonster/startuptime.vim ...

Hover/Signature with borders https://github.com/mattleong/CosmicNvim/blob/main/lua/cosmic/lsp/init.lua

Hi everyone! I’m happy to announce that CosmicNvim now includes first-class support for 4 additional themes on top of the default for a total of 5 themes to choose from! The current selection: - [Catppuccino](https://github.com/Pocco81/Catppuccino.nvim) - [Gruvbox](https://github.com/ellisonleao/gruvbox.nvim) - [Rose-pine](https://github.com/rose-pine/neovim) - [Nord](https://github.com/shaunsingh/nord.nvim) - [Tokyonight](https://github.com/folke/tokyonight.nvim) Repo: https://github.com/mattleong/CosmicNvim (⭐️’s are very appreciated!) I’ve previously said that I wouldn’t implement first class theme support for CosmicNvim outside of the default theme… Well, I guess I changed my mind. 😅 For one, it’s probably been the most requested feature. For another, I want to be able to swap and play around with themes easily as well. My initial reason for _not_ wanting to include additional theme support was because I was worried about what sort of complexity it would bring. Turns out it’s not so bad and doesn’t overly bloat the codebase. If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open [issue](https://github.com/mattleong/CosmicNvim/issues/25)!

If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open issue!

I'm currently using CosmicNvim along with Bufferline. I have bufferline configured to run `:bdelete! %d` as the close command, but event calling `:bdelete` directly has the same result: neovim is closed completely rather than just the current buffer.

You can check out my config here: https://github.com/mattleong/CosmicNvim

But I didn't do enough research on Cosmic. Installation seemed simple enough. Just git clone. So I backed up my nvim folder and installed it. Carelessly went through the installer. Decided it also wasn't for me. Rather than try to uninstall it, I renamed the folder 'nvim_cosmic' just in case, reverted back to my previous nvim folder, and there's tons of lua related errors.

And currently testing out Cosmic. Just made a backup of my nvim folder first.

Take a look at CosmicNvim! (Disclaimer: I’m the author)

Can’t think of any reasons why Cosmic wouldn’t work on WSL. Haven’t tested it though.