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.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 8753 invoked from network); 24 Aug 2022 07:07:51 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 24 Aug 2022 07:07:51 -0000 Received: from wopr.sciops.net ([216.126.196.60]) by 9front; Wed Aug 24 03:05:22 -0400 2022 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sciops.net; s=20210706; t=1661324655; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=by9ApAbrw4KTV4aAfKcGVAs3Jxst+vyTLf9xQi36Ycw=; b=mP8hdYI4M7EyXmLlBV3kipW3HOkgECMmry0UPIOY8bEvQU0vdAVdYXFE2NdYDWyDXHdM6i YRk79J9VbwJ+YPHhKUqy87PRygbTQHJuuxAzm8GyH0zo6A6LS5s/BT3axiIsA7fgPqFtdG 0LMpkUuvIHPde2KgcjZmND/LvUNGT08= Received: by wopr.sciops.net (OpenSMTPD) with ESMTPSA id f7f5804b (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO) for <9front@9front.org>; Wed, 24 Aug 2022 00:04:14 -0700 (PDT) Message-ID: <631466AA07BC8296AF8BDD0EBF0627FD@wopr.sciops.net> Date: Wed, 24 Aug 2022 09:05:14 +0200 From: qwx@sciops.net To: 9front@9front.org In-Reply-To: <8885320d-32ec-c2a4-a9d5-45f00dae080a@posixcafe.org> 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: WEB2.0 element wrapper scripting-oriented backend Subject: Re: [9front] [PATCH] programmable menus for rio Reply-To: 9front@9front.org Precedence: bulk On Wed Aug 24 07:01:48 +0200 2022, moody@mail.posixcafe.org wrote: > On 8/23/22 20:46, ori@eigenstate.org wrote: > > Quoth Jacob Moody : > >> Something I've been playing with is a way of exposing part of the rio > >> menu to the programs running within it. This is a bit of a simple > >> approach, but I would like to gauge interest that people have in > >> something along these lines before continuing. > >> > >> This adds a /dev/menu file that can be written to > >> to add new entries to the button3menu. The file > >> can be read to get the text string of an added > >> menu entry when hit by the user. > >> > >> Thanks, > >> moody > >> > > > > It seems like an interesting trick -- but, the > > programs that might use it would already likely > > be graphical, no? > > > > Switching languages via special character in ktrans > doesn't feel quite right to me. I wanted a graphical > way of switching them, and it seemed like something > I wanted on the rio menu. This is interesting. umbraticus and I experimented with adding menu2 entries in sam for commands we use all of the time. Initially I tried doing this with menu entries for adding/removing items, but it was horrible. umbraticus proposed defining a new sam command `M' which adds or removes a menu entry: as an example, `M ^R mk install' would add `^R mk install' verbatim to the menu (R being some sam script), and sending this again would remove it. We both have scripts which define a bunch of rc functions to use within sam, which also works for adding stuff at the start of a session. Then, while using sam, one can add or remove commands one ends up using a whole bunch during a session instead of switching to the command menu, finding, selecting and sending them, which happens way too often for me (for example, things like `|fmt -l 80', `|cmd |awk ...' or `!window -m -cd ... cmd', etc.). This works very nicely in my case. For rio, it's a bit different, and I don't know how it would work out or what the best interface would be, but I think it's worth discussing. Cheers, qwx