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: Tue, 23 Aug 2022 22:46:58 -0400	[thread overview]
Message-ID: <8ECB371116CD8727E72BFEDF79BC5405@eigenstate.org> (raw)
In-Reply-To: <6b1146ca-e2de-88eb-d331-e1c978baf266@posixcafe.org>

Quoth Jacob Moody <moody@mail.posixcafe.org>:
> 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?


  reply	other threads:[~2022-08-24  2:48 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 [this message]
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
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=8ECB371116CD8727E72BFEDF79BC5405@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

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