9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Michael Misch <michaelmisch1985@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] programmable menus for rio
Date: Wed, 24 Aug 2022 10:26:08 -0700	[thread overview]
Message-ID: <21D5362C-4E8B-4EBE-A9F6-A698796FD637@gmail.com> (raw)
In-Reply-To: <a9dfd625-197e-685b-8d1d-8e580a0c82bf@posixcafe.org>

I really like the concept for this type of menu. Being able to extend behaviours, without it being clunky is a hallmark feature of Acme, for example. This same mindset being extended outwards into Rio where it has been considerably more rigid in adhering to the designed usage from the outset, enables things that may not have been conceived or considered in the 90s and early 2000s when these designs were laid.

> On Aug 24, 2022, at 06:38, Jacob Moody <moody@mail.posixcafe.org> wrote:
> On 8/24/22 01:05, qwx@sciops.net wrote:
>> 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 <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?
>>> 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.
> I would 100% be behind bringing this sam work upstream.
> That is quite neat.
>> 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.
> Yeah I'm not sure what the right solution here, I'm just throwing
> out code to start the conversation.
> - moody

  reply	other threads:[~2022-08-24 17:27 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 [this message]
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:

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

  git send-email \
    --in-reply-to=21D5362C-4E8B-4EBE-A9F6-A698796FD637@gmail.com \
    --to=michaelmisch1985@gmail.com \
    --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).