New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL2 on Windows 11 -bash: warning: command substitution: ignored null byte in input #1083
Comments
@iSnackyCracky I'll try to reproduce this. What version of bash are you using? |
Found this interesting post. Will see if that works and push that change. EDIT: found an additional issue, timing indication doesn't work anymore somehow. Might need some more time. |
Wow, that was probably the fastest response I've ever gotten to an Issue <3 Bash version used is |
Yeah, I had seen this too, but didn't really understand how and where to implement it at first. I've modified the
and ran that code manually - seems to work just fine then (at least no more warnings) |
Cool, I was on the wrong path it seems. I'll push a fix! |
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. |
Code of Conduct
What happened?
I've just installed oh-my-posh on Windows 11 using winget (have been using quite an old version before, but only on windows).
It works just fine for posh and pwsh but now I tried using it in WSL (Ubuntu) with bash (using the
oh-my-posh-wsl
binary that is provided via the winget install)When I follow the documentation and just execute
(the config file is the same I'm using for pwsh on Windows)
the prompt changes (and looks just as good as expected) but on prompt (no matter if running a command or just hitting enter on an empty line) I get a
Version
oh-my-posh-wsl -version
5.8.0
Theme
custom theme (based on the default "jandedobbeleer.omp.json")
What OS are you seeing the problem on?
Windows, Linux
Which shell are you using?
bash
Relevant log output
No response
The text was updated successfully, but these errors were encountered: