Has anyone looked at this <https://arcan-fe.com/2022/10/15/whipping-up-a-new-shell-lashcat9/>
reimagining of the command line? He is trying to envisage how a shell
can evolve if it no longer has to behave like it is running on an
old-style terminal (via an emulator on a modern GUI), but has direct
access to the GUI itself.

Examples of legacy cruft that can go: there is no need to keep shell
prompts attached to previously-entered commands (and their output) --
they can disappear from the scrollback, along with misentered (failed) commands.

Also, he wants to do away with the concept of “foreground” and “background” jobs, and have the ability to enter new commands at any
time, without waiting for previous ones to complete.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 11/22/2024 18:23, Lawrence D'Oliveiro wrote:

Has anyone looked at this <https://arcan-fe.com/2022/10/15/whipping-up-a-new-shell-lashcat9/> reimagining of the command line? He is trying to envisage how a shell
can evolve if it no longer has to behave like it is running on an
old-style terminal (via an emulator on a modern GUI), but has direct
access to the GUI itself.

Examples of legacy cruft that can go: there is no need to keep shell
prompts attached to previously-entered commands (and their output) --
they can disappear from the scrollback, along with misentered (failed) commands.

Also, he wants to do away with the concept of “foreground” and “background” jobs, and have the ability to enter new commands at any time, without waiting for previous ones to complete.

This seems misguided to me. For me, the point of a shell window is to
have a log stream that can document the sequence of events.
But if he wants different features for himself, he is free to build it.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)