kitty shell and remove dev setup

[datner]

Hey, I've been getting into ssh stuff and because charmbracelet make the best ssh tools bar-none, it was a no-brainer to want to use your tools. I am also using kitty term, which has absolutely amazing capabilities that I am not willing to pass up on. Usually when ssh-ing I would drag my dotfiles so I have my env set up and ready. But it requires you use a "kitten" to ssh with: kitty +kitten ssh user@host. This ofc does not work with wishlist. So I have 2 questions:

1. How would you suggest communicating with a remote dev box? assume many dozens of dev boxes and ephemeral short-lived dev boxes with varying Linux-based OS. So lengthy setups or hacking a bash script to do it is really out of the question
2. How can I make wishlist work with the kitty kitten?

[caarlos0]

Wishlist unfortunately would not work with kitty +kitten ssh, as we don't actually call any system binaries to connect.

That being said, sendenv/setenv can be used in plain SSH config (or in the wishlist.yml configuration file), and the file copies can be done in the remotecommand.

[datner]

[Mansarde]

From the looks of it, Kitty seems to provide at least the ability to be remote controlled via unix sockets: https://sw.kovidgoyal.net/kitty/remote-control/#remote-control-via-a-socket

Go can communicate via unix sockets: https://pkg.go.dev/net#Dial

So theoretically, one could modify Wishlist to enable Kitty SSH connections via unix socket messages.

[datner]

@Mansarde I hope you don't mean me, I am not pretentious enough to believe I can maintain a fork of this

[Mansarde]

Hehe, no problem.^^ I just wanted to show that there is a way to do it without making Wishlist call (and therefore require) certain binaries to exist on the system. Maybe someone with enough competence and time might be interested enough to create a PR for this, you never know.

[caarlos0]

This is not something we have in mind for the future of the project, therefore, I'm closing it.

Thanks!