chore(shell): remove Fish configuration
Nushell is the only interactive shell now. base.shell.fish.enable stays as a deprecated no-op with a warning, because AZ-NIX-CLIENTS and AZ-NIX-SERVERS still set it and would otherwise fail to evaluate after a lock update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5b192aadfe
commit
396c41d99d
11 files changed
+15
-125
No files matched your search
@@ -142,7 +142,7 @@ If you bring a work NixOS machine into your fleet, you can use the same `m3ta-ho
|
||||
|
||||
This gives you:
|
||||
|
||||
- Your familiar shell setup (fish, starship, nushell)
|
||||
- Your familiar shell setup (starship, nushell)
|
||||
- Your CLI tools (fzf, bat, eza, zoxide, etc.)
|
||||
- Your editor configs (neovim, zed)
|
||||
- Work git identity and SSH configuration automatically
|
||||
@@ -162,7 +162,6 @@ Every module in m3ta-home has an `enable` option. Base modules default to `true`
|
||||
|
||||
```
|
||||
base.cliTools.ansible.enable # Ansible (config rollout to servers)
|
||||
base.shell.fish.enable # Fish shell
|
||||
base.shell.nushell.enable # Nushell
|
||||
base.shell.starship.enable # Starship prompt
|
||||
base.cliTools.fzf.enable # Fuzzy finder
|
||||
|
||||
Reference in new issue
Block a user