08:52 <WinterStar> Hi folks. I've been experimenting with both UWSM and systemd-run over the weekend. I however run Foot in server/client mode, and have been wondering whether there is any adverse effect if Foot as a server and all subsequent foot-clients run in individual systemd .scopes?

09:00 <dnkl> WinterStar: it's pointless. the clients don't do anything at all, except wait for the exit code of the terminal instance

09:01 <dnkl> if you launch them (the clients) with --no-wait, you won't even have any client processes

09:03 <WinterStar> this is kind of what I suspected. There would be value I assume however, in starting the program running in the terminal with an 'uwsm app --' prefix, no?

09:03 <WinterStar> or systemd-run prefix

09:04 <dnkl> yes, value, as in they'll get separated from the foot process, obviously

09:05 <WinterStar> and cleanly shut down by Systemd. Or does Foot take well enough care of cleanly shutting down running terminal applications by itself? I presume the answer would be yes?

09:06 <WinterStar> I've tried a lot of terminals, but I'm pretty impressed with how thoughtful and compliant Foot has been designed...

09:08 <WinterStar> I don't think I've ever had any other terminal as my default for this long and I never encounter any reason to switch to something else. Just to state that as a compliment ;)

09:09 <WinterStar> dnkl: I suppose my main question has been answered now. Thanks! :)

09:10 <dnkl> foot tries very hard to shut down the shell (or application) when the terminal is closed, yes. Hopefully in the right way...

09:11 <dnkl> thanks for the compliment :)