This scripts is run from shell and created my development environment
(IDE) within a new tmux session.
Don't expect documentation. It was written only for myself.
This is grown and contains fallbacks to old conventions.
Add my very first own derivation (via overlay).
Use existing scripts for dmenu.
"Build" result for nix out of the scripts,
e.g. replace references to nix dependencies.
Create proper output so nix can move it to proper places.
This was previously locally installed from repo and called with system
python3.
Can now be started as "application" which will use the installed
(patched) dmenu.
i3lock is probably broken as not whole X system is managed by
home-manager yet. It was removed and todo moved to "end".
languagetool was migrated to module. No PR was created yet
Do not create desktop item in file system, instead use proper xdg
configuration option. That way we do not need to hard code location of
file and can use a proper set with validation from module.
There is a module for htop, so use that one instead of home.file.
The cool thing is: It has "constants" for some strange integer values.
So nix version is actually readable while the generated config is
strange.
That's a cool pro of nix files.
As we add more and more files, move to set with curly braces.
Maybe home-files is a better approach, but not documented and I don't
understand it to well yet. I guess I've to create a derivation which
"builds" all the files. Maybe to complicated right now.
Might also make sense to build modules for such tools in future where I
can configure within nix, just like git.nix, and it will generate the
config. Might be cool for some things where configs might change, but
the actual things to configure might not. The generation of the file can
change within nix, while configuration within nix stays the same?! ;)
Do not hard code all values, instead configure them within home.nix.
This is more for learning purposes.
But port and allow might also be changed more frequently in general.