Meriel Luna Mittelbach

The snippet shown in the issue. My code is not the problem, as I could reproduce it in a completely empty crate as well. It gives me the error on...

Ah. I was slightly mislead by the documentation saying doc comments and *attributes* are supported, but the only example showed doc comments being placed on the static item, not the...

Found a fix `set shellcmdflag=-c shellxquote=` fixes it for me. (but zsh chokes up on some redirections due to `\` paths being passed, `shellslash` option is not applied to the...

I also noticed similar things. Have a sort of crappy windows pc with only an intel iGPU though. The window opens, but it takes a noticeable time until the first...

Alternatively, here's a hack-ish way to do it with `starship init zsh`: ```sh source

> I can confirm that I also don't see the intro screen, or to be precise, it shows for a split second and then disappears. It doesn't bother me, but...

Confirmed on my personal config, it seems to be todo-comments Closed upstream as wontfix, telling users to defer loading of the plugin in config https://github.com/folke/todo-comments.nvim/issues/210#issuecomment-1586651694 setting `event = VimEnter` fixes...

As I said, it fixes it in my config, but not kickstart. Either there are other plugins with similar issues (declaring highlight groups), or it's some kind of load order...

which-key and telescope both declare their own highlight groups I believe. That makes sense, they both have their own UIs.

My understanding is that VimEnter happens prior to the first UI draw (see also UIEnter), whereas VeryLazy happens possibly after.