dotfiles VS vim-startuptime

Personally I use yabai and skhd, which means my MacOS user experience is identical to that of another tiling window manager. Here's my config: https://github.com/ericlovesmath/dotfiles

I'm not sure if it would help, but here's mine for MacOS + Skim + VimTex, should be very similar to Windows. It is not organized in any way.

Again, I use Ultisnips with nvim-cmp, here are my snippets. I use VimTex with the pdf viewer Skim to compile the latex live side-by-side. I use this AppleScript to paste in images. nvim-cmp works very well with Ultisnips like so. That's just my personal workflow.

These are my dotfiles. I compress most of the important things inside of init.vim, although I can split that into multiple files if I wanted. after/plugin will run after my init.vim, and contains all of my plugin setup. ftplugin, aka filetype plugin will run when that filetype is opened. Ultisnips is used for my snippet manager.

I use Skim + vimtex too, here's my of that config for reference, but I don't have that issue. I'm not sure what could be causing it, but I'd imagine its an issue with compiling. Did you try opening the file with another PDF viewer to see if its fuzzy there as well?

Here's mine

My neovim config is around 350 lines long and has a couple plugins. It has a startuptime of less than 100ms. CoC and Polyglot are significantly slower than the Native LSP, which I love.

Here's my markdown config

Current dotfiles for reference: https://github.com/ericlovesmath/dotfiles/tree/master/.config/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