9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "B. Atticus Grobe" <grobe0ba@tcp80.org>
To: <9front@9front.org>
Cc: <meta.jxy@gmail.com>
Subject: Re: [9front] dangerous Exit menu item in sub-rio
Date: Thu, 18 Aug 2022 00:44:56 -0500	[thread overview]
Message-ID: <CM8WZUSGRWPX.2DAD8NILGNP97@aphrodite.pulpie.local> (raw)
In-Reply-To: <097C7F14-7AE8-4187-B043-C0BC164FE53B@gmail.com>

There are plenty of good reasons for wanting to close a sub-rio, but
keep the window, for instance, to preserve the namespace you've built
there for testing or other reasons.

Having a confirmation of some sort was discussed and rejected. While the
other options require multiple clicks, that is because they require
further inputs. The Exit option does not. No other options require
confirmation beyond the necessary inputs for them to function.

I've been using a version of this that always has an Exit option in rio
since before it was merged, and haven't managed to click Exit accidentally
even once.

If its a problem for you, just patch your local rio.

  reply	other threads:[~2022-08-18  5:50 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 [this message]
2022-08-18  5:50 ` qwx
2022-08-18  9:17   ` Steve Simon
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

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=CM8WZUSGRWPX.2DAD8NILGNP97@aphrodite.pulpie.local \
    --to=grobe0ba@tcp80.org \
    --cc=9front@9front.org \
    --cc=meta.jxy@gmail.com \
    /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).