Issue: Starship Not Found on WSL2 Launch

[philbudden]

After applying dotfiles and launching WSL2, I encounter the error starship: command not found. Interestingly, manually sourcing the .bashrc file resolves the issue and correctly initialises the Starship prompt. It seems the shell isn't loading the configuration properly on startup. This might require adjusting the dotfile setup or ensuring Starship is installed and available in the expected path during initial shell launch.

[philbudden]

Now that WSL2 allows you to run GFX apps I've installed Ghostty. This correctly initialises the starship prompt so I won't be using Windows Terminal going forward.

[philbudden]

Reopening as Ghostty is proving to be unstable when run in WSL.

[philbudden]

Fix doesn't work in devcontainers running on WSL:

bash: /home/vscode/.nix-profile/etc/profile.d/nix.sh: No such file or directory