No, I’m really happy with fish in general and use its syntax. The only times are things like e.g. a coworker sending me a 3-line script and then not being able to just copy, paste, enter.

Funny, I also went from packer to lazy.nvim, but then hopped off and redid my config in nix. Hadn’t actually heard about the default package manager. That seems like a good thing for the ecosystem!

Okay, you know what… That’s actually better than what I said. Defeat acknowledged.

(However, it still seems a bit silly to me. name="value" will prompt you to enter set name "value", with your exact name/value prefilled. As far as I know, it really is just syntax substitution; or am I wrong here? Are there semantic differences that can’t be translated?)

I’ll second Pocket-ID.

I originally had Authentik setup. It worked well enough. However, their packaging constantly broke and no-one seemed to care.

Switched to Pocket-ID and won’t be looking back. Passkey-based OAuth was all I wanted anyways. (Also, the logins themselves are noticeably faster!)

find modules/nixvim/ -name "*.nix" -type f -exec cat {} + | wc -l
3890

I’d say I’ve spent enough time configuring neovim 😄

(Btw, highly recommend configuring neovim through nixvim if you’re already using nix. Incredibly stable. I had to fix one plugin or another all the time with plain nvim. Now, literally never. Plus, nix run github:<username>/<repo>#nvim on any nix-enabled system, and get dropped into your exact config, keybinds, theme, plugins and all. I’ve set it up to expose language-enabled variants by appending e.g. .go or .python to that command.)

(Sorry my comments tend to go off-topic)

That analogy only holds if they cook the burger for you, hold it in front of you, and go “we don’t make this”, then throwing it out

I just wish fish would accept standard bash syntax in addition.

Like, if you can warn me that “this is not how we set vars in fish, do this instead!” then you could also just, you know, do it.