Kat
Kat
> Searching for a bit, I found the [`zg` library](https://codeberg.org/atman/zg) which seems to handle all text needs. Luckily for you, #5694.
Re (1), no one can figure out why `binding="strong"` breaks things for Ghostty and Ghostty only (xref https://github.com/ghostty-org/ghostty/discussions/3015#discussioncomment-12102460).
I checked both Foot and Ghostty (since those are the only two formats I'm familiar with). There were some overrides in the README for https://github.com/rose-pine/ghostty, which have been removed now...
Hi @calamitywoah, would you mind rebasing this on main?
I'm not sure if you're simply informing me where the conflict is or if you're asking for assistance on how to proceed, but regardless there's a reasonable guide by GitHub...
> could you point me to examples of those alternate main functions? I'm willing to take a shot at it, just want to be realistic about timeline since I'm still...
> Try setting the resources directory explicitly for your local build: Actually it seems to work just fine now, I'm not sure what changed. I'm not complaining I guess ¯\\\_(ツ)_/¯.
Does the environment variable propagation actually work? They're not set on the remote for me.
If I remember correctly, you need to tell SSH to propagate it in your SSH configuration, and also allow it to be set in the remote's SSH configuration too. And...
Oh also, maybe `$COLORTERM` should be forwarded too, since many people are finding that some tools don't use truecolor over ssh despite Ghostty supporting it. (`kitten ssh` does this too...