Tab completion on zsh leaves rendered completions in the window after ctrl-c

[colinmparker]

Using MacOS 15.3.1 with zsh 5.9 (arm64-apple-darwin24.0), my tab completions stay rendered in the window when I terminate the command I'm inputting with ctrl-c. Attached a screenshot below to illustrate this, and how it persists to future commands but is overwritten by subsequent renders.

Ghostty info:
Version: 1.1.2
Build: 9416
Commit: ee963f6

My ghostty config:

command = /bin/zsh
font-family = CaskaydiaCove NFM SemiBold
cursor-style = block
cursor-style-blink = false
shell-integration-features = no-cursor

[taylrfnt]

Can you share the relevant zshrc contents for your auto completion config?

I use zsh-autosuggestions and I have never had this problem while using Ghostty

[colinmparker]

I'm using oh-my-zsh with no plugins other than git. As far as I know I'm just using vanilla zsh completions. The only thing I can think of that would be relevant is that I'm using zsh-syntax-highlighting

[colinmparker]

To be clear, the reason I think this is a Ghostty issue is that I tested this with other terminal emulators like Terminal and iterm2 and didn't have this problem.

[taylrfnt]

I misread your post - I thought you were referring to suggestions, not command completions.

I'll keep trying to reproduce this, but I agree with rhodes that this sounds like another place the existing renderer issue is rearing its ugly head...

[taylrfnt]

After testing several different approaches, I was unable to reproduce this issue. I used OP's configuration, nuked my .zshrc, and tried both tip and stable releases (as well as all the possible combinations of the above). No dice. The only other thing I know to try is switching over to oh-my-zsh, but that will take some time.

[rhodes-b]

seems similar to this
#6086

[taylrfnt]

Oh, good catch! I don't know if OP is leaving the workspace like in the above issue, but it does definitely look similar.

[rhodes-b]

I dont think you need to leave the workspace
#5674 (comment)

[colinmparker]

It is similar, but it doesn't appear transparent at all so I don't know if it's actually the same issue. The opacity is the same before and after hitting ctrl-c (zero opacity)

[mitchellh]

For this, could you record an asciinema of this happening and upload the cast file?

It should NOT reproduce in other terminals, but should reproduce in Ghostty, which is indicative of a bug.