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.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4
Received: (qmail 21496 invoked from network); 18 Aug 2022 05:51:41 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 18 Aug 2022 05:51:41 -0000
Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Thu Aug 18 01:50:19 -0400 2022
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706;
	t=1660801757;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:  in-reply-to:in-reply-to;
	bh=TTSWbi9yDR/ysn2vWZJZhoUaXmEm3AJ6P3uHg9IquaY=;
	b=yjx9VMp1mZZnAyxJy3jw9yGSW6TmGbml2PaY+d4ehiJVAnpzSCxrRVOE1huXiB3HRse/cX
	InEXLakHJcTadCLPRVx/W5JWqxau4caZjAOfvp91lvkWRTRV1rQFz0ICPg5zBeKHmrUpWH
	D0iYO0f+JqyyuUc4T2rQNgX9qWROLxw=
Received: 
	by wopr.sciops.net (OpenSMTPD) with ESMTPSA id 4c706e23 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO)
	for <9front@9front.org>;
	Wed, 17 Aug 2022 22:49:16 -0700 (PDT)
Message-ID: <6E060AAEBD25BAD64BDF027734A18ECE@wopr.sciops.net>
Date: Thu, 18 Aug 2022 07:50:13 +0200
From: qwx@sciops.net
To: 9front@9front.org
In-Reply-To: <097C7F14-7AE8-4187-B043-C0BC164FE53B@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: agile configuration service-based rich-client-based solution 
Subject: Re: [9front] dangerous Exit menu item in sub-rio
Reply-To: 9front@9front.org
Precedence: bulk

On 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.

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.


> 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?

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.

Cheers,
qwx