3 ms·
> A big change is that it is communicating with the display server directly I'm curious how you imagine using this over SSH. With X forwarding? Or you'd run SS
by jstanley 4y ago
> A big change is that it is communicating with the display server directly
I'm curious how you imagine using this over SSH. With X forwarding? Or you'd run SSH inside "Lash#Cat9", and revert to a traditional shell on the remote machine?
There are some very interesting improvements in here. I especially like keeping the output of each command in its own buffer, and separating stdout from stderr. I quite frequently need to re-run a command, except pipe its output through some sort of filter. With "Lash#Cat9" I imagine I'd run the filter on the in-memory buffer instead, which could save a lot of time.
I'm not sure hiding the commands that give no output is helpful. It's quite often useful to be able to see exactly what you've done, so that you can maintain a correct mental model of the state of whatever you're doing. I suppose the "Lash#Cat9" answer would be to have the computer expose its state explicitly, rather than have the user maintain it privately.