Comment on Is there a precedent for a really delay-tolerant command line interface? (A bit off-topic)
MNByChoice@midwest.social 2 months ago
Like MOSH? mosh.org Mosh has some predictive output and will resume sessions automatically.
Or more like tmux/screen? Has some fancy “nohup” like functions.
CanadaPlus@lemmy.sdf.org 2 months ago
That’s really helpful. Thank you! MOSH might work, I’ll have to play around with it.
Could you go into more detail about the tmux functions? If it’s a way to write everything to files instead of a STDOUT in a predictable way, that would be great, since each packet could be a (compressed) shell script that explicitly includes which data to send back, if any.
MNByChoice@midwest.social 2 months ago
No, tmux does not redirect to a file. Though ‘>’ and ‘script’ do.
Tmux is like ‘screen’ and can be wrapped with ‘byobu’.
CanadaPlus@lemmy.sdf.org 2 months ago
I mean, I guess you could just programmatically insert a > after every command. That’s actually a pretty good idea. It’s kind of obvious now that you mention it, haha!
It would be better if the tools expected to be used this way, but as a quick kludge for a project about something else it’s probably sufficient.
MNByChoice@midwest.social 2 months ago
The first step is to make ot work (at all, even badly).