9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] programmable menus for rio
Date: Sat, 27 Aug 2022 15:30:20 +0200	[thread overview]
Message-ID: <CAFSF3XNKcBFniTcfs+bFS9zQZ7NKtAU2EB9KF6LPmj07ScwGhA@mail.gmail.com> (raw)
In-Reply-To: <6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org>

i have a lot of experience with a programmable / scriptable
windowmanager that is controlled via a file based 9p interface and
including the here mentioned idea of blocking event file reads.

over decades i found endless llittle tweaks for perfecting my most
common tasks and automated away repetitive interactions that are
unique to my personal usage patterns.

all using very few lines of shell scripts.

the lack of such feature in rio is what led to the obnoxious acme
application imho.

the possibilities may not seem very apparent at first glance but in my
experience a lot of small quality of life improvements add up to very
near perfect subjective user experience.

i would welcome this possibility on 9front.

  reply	other threads:[~2022-08-27 13:33 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
2022-08-27 13:30                   ` hiro [this message]
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=CAFSF3XNKcBFniTcfs+bFS9zQZ7NKtAU2EB9KF6LPmj07ScwGhA@mail.gmail.com \
    --to=23hiro@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).