Ghostty's shell integration works worse than iTerm2's shell integration, and it may be a potential bug #3759
Replies: 3 comments 2 replies
-
|
Fix by using iTerm2's integration instead of Ghostty's |
Beta Was this translation helpful? Give feedback.
-
|
Im reopening this discussion, because although I can just work around this by using iTerm's integration, I'm hoping to make ghostty an even better terminal for everyone, so I must reopen this in hopes of actually finding a real fix for the builtin shell integration, not working around it with iTerm. |
Beta Was this translation helpful? Give feedback.
-
|
We've since rewritten our Zsh integration. Is this still an issue? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ghostty has it's own built in shell integration, but on macOS, using zsh, it is 'buggy' when it comes to text redrawing, and the
cursor-click-to-movefeature doesn't work at all, basically, text redrawing when resizing the terminal and making it smaller (especially when there is alot of text printed tostdout, like when using a zsh prompt) makes the terminal look very ugly, and thecursor-click-to-movefeature simply doesn't work at all, however, when using iTerm2's shell integration and sourcing it in my.zshrcinstead of Ghostty's default shell integration, no issues occur and everything works perfectly. This is my entire ghostty config:This is the relevant part of my
.zshrc, which manually loads ghostty's zsh integration:This is the relevant script that downloads and sources iTerm2's zsh integration (which should be sourced standalone without ghostty's shell integration):
This is a video to display an example of what happens on my machine (sorry if the quality is a bit bad I used ffmpeg to compress):
output.mp4
To recreate my problem, Ghostty should have the zsh integration feature enabled by default as well as
cursor-click-to-move = truein the Ghostty config, and then iTerm's zsh integration is downloaded and sourced in the.zshrc, replacing Ghostty's zsh integration, both outcomes are compared, and iTerm's should work better, indicating that there may be a problem in Ghostty's default integration. I should also mention that I am using powelevel10k's zsh prompt. Thanks in advance for any help provided, or confirmation that this is a bug that shouldn't happen. For now I will work around this issue by using iTerm's zsh integration, but hopefully a fix in Ghostty's default one will be provided!Beta Was this translation helpful? Give feedback.
All reactions