From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] dangerous Exit menu item in sub-rio
Date: Thu, 18 Aug 2022 04:48:42 -0600 [thread overview]
Message-ID: <327fe199-bb38-c988-9514-5b6a8278fcb2@posixcafe.org> (raw)
In-Reply-To: <2CE20AEC-06B5-42B5-8764-5D5373877FB4@quintile.net>
On 8/18/22 03:17, Steve Simon wrote:
> 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
Yes mothra still has this behavior. I am not opposed to adding
a confirmation step. When the first patch was discussed I took a survey
and the leading idea seemed to just be to have it exit. I think some of
this comes down to how you use subrios. For how I use them, a premature
exit would not ruin my morning. But I can very much imagine someone having
a workflow where that would be quite the damper on their morning.
It seems to me that people that get quite a bit of mileage out of subrios
would prefer to have a confirmation exit step. For those that don't, one
more mouse click is not a painful compromise.
Thanks,
moody
next prev parent reply other threads:[~2022-08-18 10:53 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
2022-08-18 10:48 ` Jacob Moody [this message]
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
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=327fe199-bb38-c988-9514-5b6a8278fcb2@posixcafe.org \
--to=moody@mail.posixcafe.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).