> (This is somehow fixed in 1.2 but it requires additional entry in the config for whatever reason. Can't it just work?)
"For whatever reason": because it requires modifying `ssh` and doing that by default is a really sketchy thing to do because it is a very security sensitive tool. No program (Ghostty included) should be mucking with that by default. We want users to be aware.
"Can't it just work?": No, because the entire mechanism is flawed, and I didn't invent the mechanism. It's like asking, "why must I drive to my destination, can't I just teleport?" The entire premise of the question is silly, and it's not the car's fault (Ghostty is the car in this example). For those who want to learn more about "the mechanism": read Ghostty's terminfo page, but also just do some light web searching on how terminfo works. Its a total nightmare.
I really wish that weren't the case, I really do. I promise its just as annoying to me as a user and more annoying to me as a maintainer to have to hear people complain about this repeatedly when I'm not doing anything wrong, personally. I'm playing by the rules. The rules are just bullshit.
We'll continue to make enhancements to improve this while we wait for Ghostty's terminfo to propagate to every machine in the world. It will, it'll just take... a long time. Next up we plan on introducing a `ghostty +ssh` command that you can drop-in replace most `ssh` usage with and it'll automagically just work.
Ouch, I did not expect my complaining would get a response from the author!
Just to be clear, I do think Ghostty is amazing piece of software and it's so fast that it's hard to believe, so thank you for the hard work.
> read Ghostty's terminfo page, but also just do some light web searching on how terminfo works. Its a total nightmare.
Oh, yea, I totally get that. I actually _did_ try to understand what the issue is, but gave up on that time-sink rabbit hole and decided I might give it another try once the xterm-ghostty is more popular.
"For whatever reason": because it requires modifying `ssh` and doing that by default is a really sketchy thing to do because it is a very security sensitive tool. No program (Ghostty included) should be mucking with that by default. We want users to be aware.
"Can't it just work?": No, because the entire mechanism is flawed, and I didn't invent the mechanism. It's like asking, "why must I drive to my destination, can't I just teleport?" The entire premise of the question is silly, and it's not the car's fault (Ghostty is the car in this example). For those who want to learn more about "the mechanism": read Ghostty's terminfo page, but also just do some light web searching on how terminfo works. Its a total nightmare.
I really wish that weren't the case, I really do. I promise its just as annoying to me as a user and more annoying to me as a maintainer to have to hear people complain about this repeatedly when I'm not doing anything wrong, personally. I'm playing by the rules. The rules are just bullshit.
We'll continue to make enhancements to improve this while we wait for Ghostty's terminfo to propagate to every machine in the world. It will, it'll just take... a long time. Next up we plan on introducing a `ghostty +ssh` command that you can drop-in replace most `ssh` usage with and it'll automagically just work.