Closed jlucktay closed 1 year ago
I have a Bash warning popping up, but only when my working directory is inside a git repo that is checked out to a specific version tag:
bash: warning: command substitution: ignored null byte in input
To reproduce, it would go something like this in an empty directory:
git init echo "hello world" > foo.txt git add . git commit --message "foo bar" git tag v1.2.3 git checkout v1.2.3
After that, every time you press Enter and get a new prompt, the warning will show.
The warning shows up even with an extremely basic prompt configured, such as: PROMPT_COMMAND='__posh_git_ps1 "hello " "\nworld \\$ "'
PROMPT_COMMAND='__posh_git_ps1 "hello " "\nworld \\$ "'
I have $BASH_VERSION 5.0.11(1)-release and git is 2.24.0
$BASH_VERSION
5.0.11(1)-release
git
2.24.0
This would make sense. We use -z and other similar flags throughout for parsing. It may be possible to eliminate most of them or clean them up.
-z
I have a Bash warning popping up, but only when my working directory is inside a git repo that is checked out to a specific version tag:
To reproduce, it would go something like this in an empty directory:
After that, every time you press Enter and get a new prompt, the warning will show.
The warning shows up even with an extremely basic prompt configured, such as:
PROMPT_COMMAND='__posh_git_ps1 "hello " "\nworld \\$ "'
I have
$BASH_VERSION
5.0.11(1)-release
andgit
is2.24.0