To: email@example.com, firstname.lastname@example.org
Subject: Re: [9front] [PATCH] programmable menus for rio
Date: Wed, 24 Aug 2022 16:04:12 -0400 [thread overview]
Message-ID: <7A634F063FFEDFF52BC14D0DBC6A855E@eigenstate.org> (raw)
Quoth Lyndon Nerenberg (VE7TFX/VE6BBM) <email@example.com>:
> Given that rio has had a couple of decades to bake, the
> world has changed around it, and thinking of new stuff
> is always a good idea.
My point goes beyond that -- rio can be thought of as an
implementation of a more general file system interface
that can be implemented by other windowing systems.
The parsimony and focus in that interface makes it easier
to swap rio for a window system that behaves differently
but provides the same mouse and keyboard multiplexing
to the programs running under it.
Rio can -- and I think, should -- change. The interface,
though, needs to be considered with care if we want to
maintain its general nature.
Arguably, rio *also* wasn't a sufficiently good steward
of this to date.
next prev parent reply other threads:[~2022-08-24 20:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 1:40 Jacob Moody
2022-08-24 2:46 ` ori
2022-08-24 5:02 ` Jacob Moody
2022-08-24 7:05 ` qwx
2022-08-24 13:38 ` Jacob Moody
2022-08-24 17:26 ` Michael Misch
2022-08-24 17:30 ` Stanley Lieber
2022-08-24 17:37 ` ori
2022-08-24 18:56 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-08-24 19:31 ` Stuart Morrow
2022-08-24 20:10 ` Jacob Moody
2022-08-25 6:40 ` Jacob Moody
2022-08-27 3:40 ` ori
2022-08-27 13:30 ` hiro
2022-08-27 14:23 ` Mark van Atten
2022-08-27 17:22 ` hiro
2022-08-24 20:04 ` ori [this message]
2022-08-24 20:17 ` Stanley Lieber
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).