Re: [9front] dangerous Exit menu item in sub-rio

[Steve Simon <steve@quintile.net>]

maybe it still has, but mothra used to switch its cursor to a skull’n crossbones if Exit was selected - to indicate another B1 click was needed to confirm the exit, any other mouse button to cancel the exit.

-Steve


> On 18 Aug 2022, at 07:51, qwx@sciops.net wrote:
> 
> 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