| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 2022-02-21 | terminal: a few more tweaks to alacritty | Franck Cuny | 1 | -1/+10 | |
| 2022-02-13 | alacritty: switch back to white background | Franck Cuny | 1 | -0/+6 | |
| I can't stand the dark background. | |||||
| 2022-02-12 | home-manager: re-organize configuration for myself | Franck Cuny | 1 | -0/+0 | |
| 2022-02-09 | alacritty: more settings | Franck Cuny | 1 | -1/+11 | |
| 2022-02-09 | home-manager: fix some typos | Franck Cuny | 1 | -0/+0 | |
| 2022-02-09 | terminal: alacritty is our terminal of choice | Franck Cuny | 1 | -8/+1 | |
| 2022-02-09 | home-manager: simplify the configuration | Franck Cuny | 1 | -0/+18 | |
| I'm still struggling with documentation, and I'd rather have something simple that works rather than smart and does not work. The configuration for the host imports the modules that are relevant to that host (in the case of carmel, desktop and systems). For the home-manager, I create a profile "desktop" that contains stuff related to a desktop (i3, etc), and it includes the module "common" that contains stuff that I want on any machines (so that in the future, for a machine that is a server, the home manager will only import "common"). | |||||
