From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 4364 invoked from network); 27 Aug 2022 03:43:49 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 27 Aug 2022 03:43:49 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 9front; Fri Aug 26 23:40:52 -0400 2022 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-137.nycmny.fios.verizon.net [74.108.56.137]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 0ad74eeb (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Fri, 26 Aug 2022 20:40:40 -0700 (PDT) Message-ID: <6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org> To: 9front@9front.org Date: Fri, 26 Aug 2022 23:40:38 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: open-source basic template XMPP base CSS-aware layer Subject: Re: [9front] [PATCH] programmable menus for rio Reply-To: 9front@9front.org Precedence: bulk Quoth Stuart Morrow : > > 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.