9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] programmable menus for rio
Date: Wed, 24 Aug 2022 14:10:16 -0600	[thread overview]
Message-ID: <afa3cfb0-00a5-b15d-ef62-964cfd81323a@posixcafe.org> (raw)
In-Reply-To: <CABB-WO9dEVJS8F08h7HMmhAjmqwpOZwJReS_t=5g+4cVffzyHg@mail.gmail.com>

On 8/24/22 13:31, Stuart Morrow wrote:
> On 24/08/2022, Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca> wrote:
>> [ something about new /dev files ]
> I don't get why kbdtap is in rio rather than kbdfs.

I wanted information known only to rio, namely when
a user switches windows so ktrans knows when to reset the
line buffer. I originally had this communicated via
a message through kbdtap. That is no longer the case
pending me figuring a better way of communicating
this information. There isn't much of a technical reason
for why kbdtap couldn't exist within kbdfs. I do enjoy
that I can run a kbdtap program in a subrio for testing
and have it isolated there. But this has been something
I've thought about. I haven't convinced myself enough
to allot the time to do the rewrite.

On 8/24/22 12:56, Lyndon Nerenberg (VE7TFX/VE6BBM) wrote:
> 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.  But diddling with rio just seems
> a path to feechur bloat.  If you really want to try new
> things, it's best to start from the ground up (IMO).
> But the joy of rio is you can write and experiment with
> your new stuff inside of rio, without breaking your
> existing environment.

I think most would agree that a rio rewrite could be
very nice. But let's not pretend that is an easy
task. I want to be cautious about blocking any
forward movement or experimentation for some
mythical rewrite. Especially since it seems no one
has expressed enough interest to actually start
working on it.

I think I am starting to learn why people
don't enjoy working on rio. Disregarding the code, it
seems like its impossible to make a change that someone
isn't disgruntled with.

-- moody

  reply	other threads:[~2022-08-24 20:16 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 [this message]
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
2022-08-24 20:17                 ` Stanley Lieber

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=afa3cfb0-00a5-b15d-ef62-964cfd81323a@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \


* 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).