"yazi" fails to load in one and the only folder discovered to behave so thus far.

[solaSell]

I have tested this against 4 other terminals: alactritty, iTerm2, wezTerm and Kitty. They all work seamlessly. Only Ghostyy doesn't and for only the particular folder: ~Documents/obsidianNeovim/volt/Assets. See the attached screenshots



b


Does anybody have any clue why? Otherwise, Ghostty is Ghostty! Excellent terminal

[pluiedev]

Ghostty doesn't know about Yazi, but Yazi does know about Ghostty. Perhaps it's their Ghostty integration that could be the culprit.

[00-kat]

That just looks like it's used for detecting the image protocol to use though. I assume Iip = iTerm2 Image Protocol and Kgp = Kitty Graphics Protocol. Sixel is also mentioned.

[pluiedev]

Regardless, can't imagine it's our bug. Need more evidence that points towards that.

[solaSell]

On Sat, Feb 8, 2025 at 11:32 Leah Amelia Chen ***@***.***> wrote: Regardless, can't imagine it's our bug. Need more evidence that points towards that. — Reply to this email directly, view it on GitHub <#4939 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASSNMLXVGEEPXYCUPNENOKT2OXFK3AVCNFSM6AAAAABU7XBD2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJQGE4DQOI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Leah, Why does the suspicious yazi integration fail on Ghostty alone? S the evidence you're looking for the fact that Wezterm, alacritty, iTerm and kitty all pass the test?

[pluiedev]

To be honest, I don't use Yazi and I haven't studied its codebase. However, by process of elimination you can deduce that if only the combination of Ghostty + Yazi is affected, and Ghostty does zero special support for Yazi, then something is wrong on their side.

[00-kat]

It's possible Ghostty responds to some sequence Yazi uses incorrectly, or takes too long to respond, which results in it not loading; logs from a debug build would help here, though no other Yazi user has had issues on Ghostty so I'm confused why it's broken only for you.

[solaSell]

Ok. Let me rest my case. It could only be something with my own MacBook Pro M1

…

On Mon, 10 Feb 2025, 09:45 Kat, ***@***.***> wrote: It's possible Ghostty responds to some sequence Yazi uses incorrectly, or takes too long to respond, which results in it not loading; logs from a *debug* build would help here, though no other Yazi user has had issues on Ghostty so I'm confused why it's broken only for you. — Reply to this email directly, view it on GitHub <#4939 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASSNMLRX725QUZNH6YK27M32PBKJNAVCNFSM6AAAAABU7XBD2CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMJRGQ3DENQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>