vim-startuptime VS plenary.nvim

That is native and inbuild but I would suggest below options instead 1. Using lazy's Profile tab instead https://github.com/folke/lazy.nvim 2. Using a dedicated plugin to do this https://github.com/dstein64/vim-startuptime. 3. Using an external program hyperfine is one that I use https://github.com/sharkdp/hyperfine

This plugin https://github.com/dstein64/vim-startuptime

dstein64/vim-startuptime (which I never use, my startup time is under 130ms, which is sufficient)

Use the plugin with the flag --tries 100. Also, what are the first 10 lines of output from running the above command? I'll start.

only today I tried this plug to test startup time and got this result:

dstein64/vim-startuptime: ⏲️ A Vim plugin for profiling Vim's startup time.

Using vim-startuptime to profile, I get these startup numbers on an Apple M1 Macbook:

Oh sorry, I already solved my issue but forgot to delete the post! But to answer your question: Of course! It's https://github.com/dstein64/vim-startuptime. You can either launch nvim with nvim --startuptime outputfile.log FILENAME to get detailed diagnostics in the file outputfile.log or just call :StartupTime after nvim/vim has started up to get this graph. It's pretty neat and easy to use!

You could try to install this plugin temporarily : https://github.com/dstein64/vim-startuptime

we can create a function to open a pop up menu using plenary.popup like this, you need to install neovim plenary if you don't already have it https://github.com/nvim-lua/plenary.nvim

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

I feel this :( That said, alot of plugins rely on plenary.nvim. Its up to you if you determine this is "non-essential" or not. It will almost certainly be available for you to use already.

The big reason I ask is that reaching out to an external python shell to run commands (disregard the fact that its python running) is going to be much slower than using the in built lua JIT interpreter. Additionally, plenary has a built in curl function so you don't have to "reinvent the wheel".

There is also test harness in nvim-lua/plenary.nvim with a slightly different design, but still usable of course.

I am simply using busted or more specifically vusted which is a wrapper around busted for Neovim. It should be quite straightforward to learn the basics, I would say you mostly need to know these functions: describe, it (these are used to structure your test cases) and assert.are_same (to check for table equality). Some people are also using plenary which is also based on busted.

It's based on nvim-lua-plugin-template, but uses Nix flakes to run plenary.nvim tests.

Plenary plugin for Nvim