Junk character on first line output

[NgoHuy]

I have this issue recently, when I use fzf with bash. After pressing Ctrl+r to search history, the output will have some junk on that. My shell is bash.
I debugged it and found that it started with --posix as default with no profile. and the bug is somewhere on bash-preexec.bash. Because when I start new bash freshly or source ghostty.bash without source bash-preexec.sh, it works fine

[jparise]

I can reproduce this. I also think the junk is coming from the PROMPT_COMMAND (precmd) stuff, but we'll need to dig into why this is only causing a problem when the shell integration is injected.

[jparise]

I don't think this is directly caused by the automatic shell integration. I can still reproduce this with shell-integration = "none" and then manually sourcing ghostty.bash.

[mitchellh]

I don't think this is directly caused by the automatic shell integration. I can still reproduce this with shell-integration = "none" and then manually sourcing ghostty.bash.

Yes I believe it’s in the shell integration bash code not the injection part. It’s just becoming more prevelent because more people are testing code paths now.

[NgoHuy]

But when we dont source it, it still worked. When We create new bash envit worked too.