9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] programmable menus for rio
Date: Fri, 26 Aug 2022 23:40:38 -0400	[thread overview]
Message-ID: <6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org> (raw)
In-Reply-To: <CABB-WO9dEVJS8F08h7HMmhAjmqwpOZwJReS_t=5g+4cVffzyHg@mail.gmail.com>

Quoth Stuart Morrow <morrow.stuart@gmail.com>:
> I don't get why kbdtap is in rio rather than kbdfs.

It needed to be somewhere, and rio is somewhere.

There are some advantages to putting it in rio, there
are some advantages to putting it in kbdfs, but in the
end, the interface seems to be exactly what is needed,
and if there's a clear advantage it can be moved with
no change in interface. And the interface being right
is the most important thing, since it admits a number
of implementations.

If you feel strongly about moving it out of rio, I
think it'd be possible to send moody a patch along
with a strong argument to move it.

  parent reply	other threads:[~2022-08-27  3:43 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 [this message]
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=6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org \
    --to=ori@eigenstate.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).