How about minimal template?

[datacurse]

im trying to grasp config right now and its a bit scary. There are different categories and stuff. Would be nice if there was a minimal config template such that someone would only add plugins. In lazy i used to just stack plugins in one folder by adding configs, that was pretty convenient and clean.

[datacurse]

There are also different package definitions? I would only use one nvim config. Im a bit afraid to delete something that i thought was not essential and it actually was. The most minimal functional version would be good.

[BirdeeHub]

https://github.com/BirdeeHub/nixCats-nvim/tree/main/templates/home-manager

Does the one in the home manager template count? I just added it a day or 2 ago and you might not have seen it yet.

If not, what would you like to see? Are there changes to other existing templates you can think of that would make them more understandable?

I feel that, while the existing examples are great who used neovim before nixos, they are less great for people who havent and I was hoping the one I just added to the home manager config could help adress that?

Should I also add one to the flakeless or nixos module templates that doesnt use lazy loading? It would probably take another 100-150 lines off of that config in home manager and simplify it a bit further?

Edit: see also https://github.com/BirdeeHub/nixCats-nvim/tree/main/templates/simple

[BirdeeHub]

you suggest to use 2 package versions so that one updates lua in real time, and another only on builds so that i would have a backup in case something is fucked up?

Yeah. Because it is very easy to have 2 identical outputs outside of those 2 settings (if copy pasting 2 copies of the entry is annoying you can factor it out too) it ends up being nice to have 2 separate outputs, 1 for testing 1 for being the final installable, especially because it then gives you a backup as well.

do you use vi for wrap false and vim for wrap true or the other way?

I use vi for wrapRc = true because the wrapRc = true version is the one you should be running most of the time for reproducibility unless you are editing, so shorter is better. But to be honest, on a computer where you are going to have the config cloned locally either way, it doesnt much matter which you are running other than the fact that 1 reflects lua changes immediately, the other needs a rebuild

the one with yy. Because of this line when you enter y it does not work, and you already have Y for that functionality.

This is certainly odd because its not causing an issue for me? I might have another setting that is set which you removed that is solving that though (which is fine of course, its your config, but possibly the case as to why its behaving differently)

That can be removed yeah. I think its not necessary as "+y can still take a subsequent motion, which I think includes a second y

[BirdeeHub]

As far as running it as a separate flake goes

There isnt necessarily any advantage? You can still install your config, and export your derivation from your system flake for running via nix run if you do it the way you did, just pass it to where it needs to go.

I keep mine as a separate flake so that I dont have to link people into a subdir of my cursed system configuration to show an example from my neovim config

The other advantage is that for new users, its nice to have a separate thing that they can run separately of a config, and see what the flake exports in the repl.

It also proved difficult to explain to people how to integrate a configuration in which I have no idea how it will be structured, (its their config, they could have structured it in literally any way) so "install it from your flake" ended up being easiest to explain

Honestly, folding it into your main config as you did is often the way to go.

[BirdeeHub]

Also, you can get all of the packages in packageDefinitions if you want to choose which ones to include

nixCats.utils.mkAllPackages (import /home/loki/.config/nixCats-nvim { inherit pkgs; })

^ returns a set with all the packages by their name in packageDefinitions

/home/loki/.config/nixCats-nvim

^ also as a flake user, this freaks me out unless its in the repl XD

Why is it not a relative path within this flake, it could just like... not be there!

Wild that you can just import from a non-store path like that in impure nix. I kinda dont like that XD But to each their own.

[BirdeeHub]

#160 (reply in thread)

done by the way

the top 3 keybindings in that snippet can be replaced by this one

vim.keymap.set({"v", "x", "n"}, '<leader>y', '"+y', { noremap = true, silent = true, desc = 'Yank to clipboard' })

lmao thanks for pointing it out

[datacurse]

Wild that you can just import from a non-store path like that in impure nix. I kinda dont like that XD But to each their own.

i have absolutely no idea what im doing :3