world.git - nix configuration for my machines

	Commit message (Collapse)	Author	Age	Files	Lines
*	home/shell: switch the default shell back to zsh	Franck Cuny	2023-03-11	1	-1/+1
\| \| \| \| \| \| \| \|	I keep running into issues when using fish: I'm not familiar with the syntax and I don't use it enough that it sticks. I also need to google stuff regularly to figure out how things are supposed to work. This is annoying enough that the supposed benefits of fish are not worth it for me.
*	feat(hosts/home): use fish as my default shell everywhere	Franck Cuny	2022-06-23	1	-1/+1
\| \| \| \| \| \| \|	Change-Id: I75df9d3ba133e3f7380a518e1b8c70a564f60482 Reviewed-on: https://cl.fcuny.net/c/world/+/481 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
*	ref(home/shell): make it easier to share common things between shells	Franck Cuny	2022-06-20	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	I'm considering trying again fish, and there are a number of things that should be common between zsh and fish (aliases, environment variables, ...). Instead of duplicating these settings multiple time, I'm consolidating the shell configurations under `home/shell`, and I can set the shell I want to use with `my.home.shell.name`. The first step is to move the modules for fish and zsh under `home/shell`, add an interface to pick which one I want to use, and modify the `host/home.nix` configuration to keep using zsh with the new interface. Change-Id: Idb66b1a6fcc11a6eeaf5fd2d32dd3698d2d85bdf Reviewed-on: https://cl.fcuny.net/c/world/+/455 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
*	ref(home): structure and add comments	Franck Cuny	2022-06-09	1	-2/+11
\| \| \| \| \| \|	Change-Id: I9abd49136df79a9ed040c9ec0e12eea30736c9ff Reviewed-on: https://cl.fcuny.net/c/world/+/295 Reviewed-by: Franck Cuny <franck@fcuny.net>
*	zsh: switch to zsh as the default shell	Franck Cuny	2022-05-15	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	`zsh' is available everywhere and is compatible with bash. When using `fish' I need to remember how to do things. While the completion style is nicer, I don't care about the rest. I prefer to have a consistent experience in the shell, no matter where am I. This is an initial configuration, I might need to make a few changes as I go.
*	syncthing: don't run from home	Franck Cuny	2022-04-21	1	-1/+0
\|
*	syncthing: let's run it from home-manager	Franck Cuny	2022-04-21	1	-0/+1
\|
*	initial attempt to reconfigure home-manager	Franck Cuny	2022-04-07	1	-0/+17
	All the modules that are needed for home-manager should be under `home/`, and each host will have a `host.nix` where the modules are enabled as needed. Later on we can create some profiles to make it easier to consume the configuration. I apply this only to tahoe for now, as the amount of packages needed for my user are pretty limited.