• smiletolerantly@awful.systems
    5·
    9 hours ago
    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)

    • lemonhead2@lemmy.world
      1·
      5 hours ago

      interesting how things change. i started out downloading scripts from vim.org before the github days. finally after 10years I got fed up and looked for a plugin manager. moved to packer.

      a couple of years later, that went dead so I was forced to move again. now I’m on lazy.nvim which works well for me.

      nvim decided to ship a default plugin manager. im dreading the day I have to migrate to that… (not cause it’s better/worse, but cause migrating is a pain)

      • smiletolerantly@awful.systems
        1·
        4 hours ago

        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!