nixos-config - My NixOS system configuration, with some of my binaries

	Commit message (Collapse)	Author	Age
*	style(treewide): Format	Benedikt Peetz	2024-05-25
\|
*	fix(treewide): Use `nixVersions.latest` instead of just `nix`	Benedikt Peetz	2024-05-25
\| \| \| \| \| \| \|	`nix` is an alias (in `all-packages.nix`) to `nixVersions.stable`. `nixVersion.latest` is always the last released version of nix. I obviously want that `nix` with more features (and slightly more bugs probably).
*	fix(pkgs/by-name/ya/yambar-{memory,cpu}): Add devshell	Benedikt Peetz	2024-05-25
\|
*	build(treewide): Update	Benedikt Peetz	2024-05-25
\|
*	fix(pkgs/update.sh): Update to the new `by-name` convention	Benedikt Peetz	2024-05-24
\|
*	fix(pkgs/by-name/{tr,ya}): Move away from `crane.lib.${system}`	Benedikt Peetz	2024-05-24
\| \| \| \|	It's deprecated.
*	style(treewide): Reformat	Benedikt Peetz	2024-05-24
\|
*	fix(pkgs/by-name/na/neorg): Adapt values to the `by-name` change	Benedikt Peetz	2024-05-24
\|
*	refactor(pkgs/by-name/vi/vim-plugins): Give nixpkgs compatible name	Benedikt Peetz	2024-05-24
\| \| \| \| \|	Nixpkgs already provides `vimPlugins` so having a `vim-plugins` set is rather confusing. Calling it `vimExtraPlugins` resolves this confusion.
*	feat(pkgs): Pull yambar-{cpu,memory} in tree	Benedikt Peetz	2024-05-24
\|
*	refactor(pkgs): Categorize into `by-name` shards	Benedikt Peetz	2024-05-23
	This might not be the perfect way to organize a package set -- especially if the set is not nearly the size of nixpkgs -- but it is _at_ least a way of organization.