git segment missing

[ffes]

Today I upgraded to the 8.36.4 but I'm not sure what the previous version was. Must have been a version in 8.x somewhere.

Since that my git segment is not showing anymore, all the other segments seem to work. The config hasn't changed since early April. I am not sure if I have missed something in the docs and need to update my config, or if this is a problem and need to open an issue.

Seeing this problem with oh-my-posh on WSL2 on Win10 in Windows Terminal (although it seems strange that it is related to the OS).

[lewis-yeung]

Found a bug there. I'll create a PR to fix it.

[lewis-yeung]

@ffes Please wait for #2727. After it lands, update Oh My Posh and try again. :)

[ffes]

Thanks. I see it is OS related and it was a recent change.

Obviously I will let you know

[lewis-yeung]

@ffes I guess the last working release is v8.36.1, right?

[ffes]

Just tested the whole v8.36.x series. With v8.36.2 it still worked, with v8.36.3 the segment disappeared.

Note that I update oh-my-posh in another tab

[lewis-yeung]

@ffes A new version is live now.

[ffes]

On my laptop at work, where I encountered and reported the problem, v8.36.5 works as expected for repos in my $HOME directory. But for a git repo in /mnt/c/Source it doesn't work. The git segment disappears there as well. I must say I didn't try that path before, because I didn't have the time to do so yet. Hopefully tonight I will have some time to dig in this a bit more.

[lewis-yeung]

But for a git repo in /mnt/c/Source it doesn't work. The git segment disappears there as well.

@ffes Actually, the answer is simple: /mnt/c/Source is a WSL shared path, so Oh My Posh will call the Windows Git executable (git.exe) instead of the Linux one (git). This is for performance reasons, see #1486 for details.

Do you have appendWindowsPath = false in the [interop] section of your /etc/wsl.conf? Or you may have disabled execute permissions of all files in Windows filesystem (e.g., options = "metadata,umask=22,fmask=111" in the [automount] section, which is what I use). Since git.exe is not found in your WSL PATH, which is reported in the debug logs you provided:

2022/08/30 11:54:23 error: CommandPath
not relevant
2022/08/30 11:54:23 CommandPath duration: 12.765523ms, args: git.exe
2022/08/30 11:54:23 HasCommand duration: 12.768391ms, args: git.exe

the segment will definitely not be rendered. 😆

[ffes]

Make sense. Git for Windows was installed together with Visual Studio when I started using this machine. Apparently it wasn't added to the path than. I never use GfW from anything else then the Git Bash, so I never missed it in my path either. Thanks for the info.

[ffes]

Thanks again for the quick replies and fixing the problem