From: Steve Simon <email@example.com>
Subject: Re: [9front] dangerous Exit menu item in sub-rio
Date: Thu, 18 Aug 2022 11:17:01 +0200 [thread overview]
Message-ID: <2CE20AEC-06B5-42B5-8764-5D5373877FB4@quintile.net> (raw)
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.
> On 18 Aug 2022, at 07:51, firstname.lastname@example.org wrote:
> On Thu Aug 18 07:34:32 +0200 2022, email@example.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.
next prev parent reply other threads:[~2022-08-18 9:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 5:34 Xiao-Yong Jin
2022-08-18 5:44 ` B. Atticus Grobe
2022-08-18 5:50 ` qwx
2022-08-18 9:17 ` Steve Simon [this message]
2022-08-18 10:48 ` Jacob Moody
2022-08-18 11:46 ` Jacob Moody
2022-08-18 11:56 ` qwx
2022-08-18 13:46 ` igor
2022-08-18 13:51 ` ori
2022-08-18 13:59 ` Stanley Lieber
2022-08-18 15:52 ` igor
2022-08-18 22:33 ` Stuart Morrow
2022-08-18 15:59 ` Jacob Moody
2022-08-18 16:18 ` Stanley Lieber
2022-08-18 16:22 ` Kurt H Maier
2022-08-18 16:57 ` Frank D. Engel, Jr.
2022-08-18 17:02 ` Stanley Lieber
2022-08-18 21:53 ` the lemons
2022-08-18 16:43 ` kvik
2022-08-18 22:30 ` Stuart Morrow
2022-08-18 15:16 ` qwx
2022-08-26 6:48 ` mkf9
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).