From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 15276 invoked from network); 18 Aug 2022 09:18:38 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 18 Aug 2022 09:18:38 -0000 Received: from mx2.mythic-beasts.com ([46.235.227.24]) by 9front; Thu Aug 18 05:17:07 -0400 2022 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=quintile.net; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=wfGRgK5ioGwdbWnoIgtm4Makmg+7UkrOntc2w95+7EA=; b=JBHYhyZFLwcWweNVT2Eqg4Y8S2 UxztUmEg33j9gQp5Bo2q/NtG9qVsz5md8K8hYddTSunj4gDutHdADmM6vI5iI6O/JEyBSbTRQtPL8 FyIZywjG/nJQEXbF12PLmiM3tgGRBU4t8k3Dp48vj/bHx1m723QBPAa9bwVAi96eSA1UbMD9b2xvd XNbiY5qY+i1dVdo5cslb7Sw1CH7hykk+4EvXNcAKFhDwGFHsRqOTvXwyCZFYKuLyyjNgtsKHYxWfx VGip+lRq7iBZOYIuFdH1RZmXwi4wnlCfSTPaYvr1FHmTELKUfH+GdkXaqHTR+7QI2H7LKojc/Npd7 WrbFYe9A==; Received: from [85.255.233.148] (port=61472 helo=smtpclient.apple) by mailhub-hex-d.mythic-beasts.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oObeD-00CJvt-Ad for 9front@9front.org; Thu, 18 Aug 2022 10:17:05 +0100 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Steve Simon Mime-Version: 1.0 (1.0) Date: Thu, 18 Aug 2022 11:17:01 +0200 Message-Id: <2CE20AEC-06B5-42B5-8764-5D5373877FB4@quintile.net> References: <6E060AAEBD25BAD64BDF027734A18ECE@wopr.sciops.net> In-Reply-To: <6E060AAEBD25BAD64BDF027734A18ECE@wopr.sciops.net> To: 9front@9front.org X-Mailer: iPhone Mail (19G71) X-BlackCat-Spam-Score: 4 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: NoSQL-scale interface-scale blockchain Subject: Re: [9front] dangerous Exit menu item in sub-rio Reply-To: 9front@9front.org Precedence: bulk maybe it still has, but mothra used to switch its cursor to a skull=E2=80=99= n crossbones if Exit was selected - to indicate another B1 click was needed t= o confirm the exit, any other mouse button to cancel the exit. -Steve > On 18 Aug 2022, at 07:51, qwx@sciops.net wrote: >=20 > =EF=BB=BFOn Thu Aug 18 07:34:32 +0200 2022, meta.jxy@gmail.com wrote: >> Right click in sub-rio now becomes quite dangerous, >> an accidental release of the right button when the >> mouse cursor is on the Exit menu item will destroy >> everything in that sub-rio. >=20 > I agree and this had been the reason why it wasn't accepted in the > past, though it wasn't for subrios alone. I strongly suggest adding a > confirm click or something if this is kept. >=20 >=20 >> The most dangerous item in the menu requires the least >> effort to trigger. Do we really need such convenience >> in destroying sub-rio? How often do you destroy the >> sub-rios? What's preventing using the parent rio's >> Delete menu item for this? >=20 > I use subrios quite heavily and I need it *all of the time*. In some > circumstances, one ends up having to find the subrio's pid and kill(1) > it, even within itself. One silly example is a rio started while > rcpu(1)'d, same with vnc. Others include scripts starting subrios and > cleaning up after themselves. You can jump through hoops and > accomplish the same thing, but after years with it, I think Exit is > massively useful. I do think that there should be some safeguard > mechanism though. >=20 > Cheers, > qwx