Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lars Poulsen <lars@beagle-ears.com>
Newsgroups: comp.unix.shell
Subject: =?UTF-8?Q?Re=3A_Whipping_Up_A_New_Shell_=E2=80=93_Lash=23Cat9?=
Date: Thu, 5 Dec 2024 06:59:43 -0800
Organization: AfarCommunications Inc
Lines: 20
Message-ID: <visf50$1lubp$1@dont-email.me>
References: <vhrebp$1e66s$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 05 Dec 2024 15:59:45 +0100 (CET)
Injection-Info: dont-email.me; posting-host="c26e061e8c27299e91d0ac92392868f0";
	logging-data="1767801"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19AcXf2MfTgh8pgQXub4bWj1AwkudQyIH4="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:MLag+w3wMOqx8W380xxQ5yTUpEQ=
In-Reply-To: <vhrebp$1e66s$1@dont-email.me>
Content-Language: en-US
Bytes: 2053

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.