Closed tig closed 4 years ago
There's a environment variable you can look for: WSL_DISTRO_NAME
. If that one's set, you know you're inside of the WSL. I'll add that context for sure to go-my-posh.
There's a environment variable you can look for:
WSL_DISTRO_NAME
. If that one's set, you know you're inside of the WSL. I'll add that context for sure to go-my-posh.
Awesome. And now I know about go-my-posh. What rock have I been under?
Does go-my-posh completely replace oh-my-posh?
Does oh-my-posh now USE go-my-posh?
Does go-my-posh completely replace oh-my-posh?
Not yet, but I intend to do that once we're somewhere on feature parity (only the git segment needs a few additions) That means that it will indeed use go-my-posh underneath as the go-my-posh powershell package already does that.
What rock have I been under?
To be fair, I'm only open about this for a month or so :-)
What happens if both oh-my-posh and go-my-posh are installed?
What happens if both oh-my-posh and go-my-posh are installed?
You can choose which one to use. They do not conflict with each other in terms of commands.
I use PowerShell both in Windows and WSL. My host name and user is the same in both.
Can I change the prompt on Linux to show that I'm in WSL?