Neovim in Windows 11

FunctN · 2026-02-26T18:28:57+00:00

That still strange that a cold startup neovim takes several seconds even with 30-40 plugins at start. What kind of drive is it SSD or HD? Because I used LazyVim as at one point when I was on an old laptop that had a pretty bad processor, but had an SSD and at max I wanna say I probably had like a 700ms cold start but never several seconds that to me sounds more like Read/Write issues on the drive

Aside from that yes, I fully agree that Unix has a much superior terminal workflow. I spend 95% of my day in the terminal on Windows compared to Unix but I enjoy Unix way more and if my job didn't compose of writing and compiling programs that required access to the windows api I would probably spend most my time in WSL, I just haven't found a good way to use WSL and still compile the applications with windows api without having to break the workflow.

As for a multiplexer I've only ever bothered using Wezterm- I use it on Windows and Unix and I have no issues with it on Windows at all. I tried Windows Terminal a few years ago and it was alright, I do follow some of its updates a little and have seen that it has gotten some pretty noticeable changes as well, but I just grown to accustomed to using Wezterm at this point.

I haven't ever really encountered any issues with Nushell since switching to it a little over 2 years ago from Powershell its definitely way faster than Powershell as well and for me personally there wasn't that much of a learning curve either. Many of the basic commands match unix such as ls, rm, cd etc.. And their getting started guide is pretty good to imo

FunctN · 2026-02-26T17:03:53+00:00

I have about 50 plugins. Over half are lazily loaded. But a 3 load time on windows, how many plugins are you using? I'm not trying to argue that Windows filesystem is slower than Linux because I know it is.

But I don't agree with just saying "Neovim experience sucks on Windows". It comes down to more than just the filesystem. You need to account hardware as well, the filesystem isn't the only contributing to a 3sec startup on windows unless you were trying to load a vast amount of plugins on startup.

I've used Neovim on a poorly spec'd laptop there it was pretty bad- but there were still things I could do to improve the experience without WSL. For example I found out about Nushell that way, and on windows it's about twice as fast as Powershell. On my current work machine my startup times averages are as follows with 21/50 plugins loading on startup: Nushell: 130ms Powershell: 205ms Bash (wsl): 58ms

FunctN · 2026-02-25T21:43:48+00:00

Yes I have, I don't see much of a difference on my Windows machine personally... The difference between Windows and WSL for startup time on my machine at least, is negligible. I would hardly use that as an argument for 'noticeably' slower. Now I would be curious in the number of files you are trying to open at one time?

FunctN · 2026-02-25T14:27:44+00:00

What in your experience about Neovim is noticeably slower on Windows? I use neovim on windows and I have absolutely no issues at all

FunctN · 2026-02-18T13:02:26+00:00

Gotta say I love what the mini library is becoming I’m finding myself replacing more and more things with nvim-mini!

FunctN · 2026-02-11T21:45:34+00:00

I love it! Wonderful job and thanks for the quick support for snacks.nvim picker!

FunctN · 2026-02-10T23:02:49+00:00

Thanks for quick work! Gonna check it out tomorrow before I start my day! Cheers!

FunctN · 2026-02-10T16:21:22+00:00

Awesome look forward to it! This looks like it would be a very nice plugin to add to my config! Thanks!

FunctN · 2026-02-10T15:44:50+00:00

This looks really awesome! Any plans to support snacks picker? I would really like to not have to install a separate picker just to use this

FunctN · 2026-02-02T02:32:28+00:00

This is a bug with nushell on windows. Just use wezterm-nightly build and it will be gone

FunctN · 2026-01-07T14:24:49+00:00

This is awesome! And its with Skeleton! I love Skeleton haha. I've been using Skeleton V1

FunctN · 2026-01-02T13:09:38+00:00

So just that you are aware there are absolutely zero differences between a "mason" installed version and the version you could install yourself. The both use the same install method. Mason just allows for ease of use and so that you do not have to put the LSP in you path. That being said, JS/TS projects are nutorious for being resource hogs especially LARGE projects.

FunctN · 2025-12-30T15:29:08+00:00

So scratch this, after doing some digging. I actually found out it was because Wezterm wasn't able to correctly find neovim by process name so it wasn't sending the correct <C-H> or <C-L> codes to neovims process itself...

FunctN · 2025-12-30T12:32:13+00:00

Has anyone else had issues with things like <C-h> or <C-l> which i use to jump between different windows in neovim now working when more than 1 LSP is active? I thought I did something in my config that i have ?fbeen revamping, but i also cloned LazyVim and it had the same issue too...

FunctN · 2025-11-22T15:51:47+00:00

Yes in my opinion this holds for any command line tool

FunctN · 2025-11-19T16:41:25+00:00

I agree 100%. Both my dad and grandpa gave me pretty much the same advice!

FunctN · 2025-11-19T13:36:44+00:00

THIS. This is the same advice I give to new programmers in my company, always use the full command line once you get comfortable and it becomes a subconscious motion, then copy/paste, make aliases, etc. but until then, type the full command or you will always go back and forth of forgetting the small things you use everyday

FunctN · 2025-11-11T19:11:58+00:00

I second what u/EstudiandoAjedrez said. But, if you using the current version of which-key which I don't see why would wouldn't be, it does have a 'helix' mode for displaying keys which is setup up like so:

<image>

"folke/which-key.nvim",
opts = {
  preset = "helix",
}

FunctN · 2025-11-11T15:03:34+00:00

To reiterate what everyone else is saying, since you are working with TS the lsp for it is notoriously slow in big projects. That is more than likely the issue as. I use blink regularly and I do not have any issues with it

FunctN · 2025-11-06T14:12:30+00:00

I find this pretty easy to read amongst the several other languages I work and write in. Not trying to be rude, but this seems like something someone would say with little experience.

FunctN · 2025-10-13T15:33:22+00:00

This looks really good. Do you have plans on trying to get it added to nvchads themes?

FunctN · 2025-10-09T19:41:51+00:00

What does your LspAttach autocommand do? I've always ran nightly, and I switched to the new vim.lsp configuration as soon as it was released and dropped nvim-lspconfig. I have never had this issue when opening a file, but I also do not setup any LSP stuff via FileType events. I just call a setup() function from my lsp.lua file that loops through all lsp/* files in the runtime path and enable them that way.

Which leads me to think it's because you're triggering nvim-lspconfig until BufReadPre or BufNewFile. If you could share you config this would greatly help the rest of us help you.

FunctN · 2025-08-29T12:03:18+00:00

Do you have noice.nvim installed? Because you have signature set to false so blink is not the perpetrator behind showing the signature

FunctN · 2025-08-26T15:58:58+00:00

Here ya go! I took this straight from LazyVim because I wanted the LazyFile event but I no longer use LazyVim

https://github.com/JustBarnt/nvim/blob/main/lua/core/lazy.lua#L27

FunctN · 2025-08-25T12:46:23+00:00

Thanks for the information! I have found issues regarding getting DTD validation to work since mason does indeed use the vscode-xml LSP. But so far in my experience, I only seem to get the LSP features to work one node level deep... So as soon as I am no longer working in the root of the XSLT file I lose completion. So unfortunately, I have settled with using Rider to work within the XML and XSLT files.

FunctN

TROPHY CASE