Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | home/shell: a few more tweaks to zsh | Franck Cuny | 2023-03-14 | 1 | -2/+2 |
| | |||||
* | home/shell: aliases and cleaner prompt | Franck Cuny | 2023-03-12 | 1 | -1/+1 |
| | |||||
* | home/shell: switch the default shell back to zsh | Franck Cuny | 2023-03-11 | 1 | -1/+8 |
| | | | | | | | | 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. | ||||
* | fix(new-lines): add or remove new lines where needed | Franck Cuny | 2022-07-02 | 1 | -1/+0 |
| | | | | | | | | | | | The pre-commit hook for new lines reported and correct a number of issues, so let's commit them now and after that we ca enable the hook for the repository. Change-Id: I5bb882d3c2cca870ef94301303f029acfb308740 Reviewed-on: https://cl.fcuny.net/c/world/+/592 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 | -0/+11 |
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> |