I am using the new windows terminal.
I just installed powershell v7.0.2 and starship to make it better.
I want to edit the starship config, so I ran this command:
> starship.exe config
----------------------
Error: editor "vi" was not found. Did you set your $EDITOR or $VISUAL environment variables correctly?
Full error: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }
So I went ahead and edited my $PROFILE to set visual studio code as the default editor (code is in the path):
> code $PROFILE
---------------
$ENV:EDITOR = "code"
$ENV:VISUAL = "code"
Now I get the same error but with code instead of vi:
> starship.exe config
----------------------
Error: editor "code" was not found. Did you set your $EDITOR or $VISUAL environment variables correctly?
Full error: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }
The reason I ended up running starship config is because after creating the $HOME\.starship\starship.toml config file, starship ignores it, although I've set the path in my profile:
> code $PROFILE
---------------
$ENV:STARSHIP_CONFIG = "$HOME\.starship"
So I ran starhip config to see which is the path that it expects the config file to be in.
I also tried to set the full path to visual studio code in $EDITOR, but it didn't help.
starship.tomlconfig file (which I created in the documented path) seams to be ignored bystarshipand I wanted to open in through thestarship configcommand so I can see the actual filename and path that it expects to find the config in.