From: Ori Bernstein <ori@eigenstate.org>
To: 9front@9front.org
Cc: kvik@a-b.xyz
Subject: Re: [9front] Bounties
Date: Wed, 22 Jan 2020 09:04:06 -0800 [thread overview]
Message-ID: <20200122090406.ed8c917dc4f88e511a1b85ef@eigenstate.org> (raw)
In-Reply-To: <EFC0BF3379A3C032D5568E0E5CB5D3A1@a-b.xyz>
On Fri, 17 Jan 2020 17:05:05 +0100, kvik@a-b.xyz wrote:
> > I don't suppose it's hard to write a filter for /dev/kbd in C.
>
> Indeed.
>
> > It would have to run before rio.
>
> There is your problem.
>
> The proverbial shortcut machine needs to have a target rio -- actually a
> current window -- bound in its namespace if it is to boss one around.
>
> I can imagine some elaborate scheme to work around this, taking into
> consideration the possibility of having lots of (sub)+rios, but... this
> is about as elegant as adding shortcuts you want to rio.c and calling it
> a day.
>
> --
> kvik
>
Another option is to just make things more programmable.
For example, if you had a writable /dev/$winid/kbd, and a /dev/prekbd which
let you insert a keyboard, when opened, would feed keyboard events into
your keyboard shortcut program instead of into the focused window, you
could do whatever you want.
--
Ori Bernstein
next prev parent reply other threads:[~2020-01-22 17:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` Ethan Gardener
2020-01-17 16:05 ` kvik
2020-01-17 21:55 ` Silas McCroskey
2020-01-18 0:23 ` rio wishlists Lyndon Nerenberg
2020-01-18 0:40 ` [9front] " Stanley Lieber
[not found] ` <CAFSF3XNfdhb+ViOBmVMQ+5+PnSjCeD+9a9p9e4Ug0EX9==aZvw@mail.gmail.com>
2020-01-18 8:19 ` hiro
2020-01-18 9:53 ` Steve Simon
2020-01-18 10:19 ` hiro
2020-01-21 8:54 ` Ethan Gardener
2020-01-21 8:57 ` Ethan Gardener
2020-01-21 9:49 ` hiro
2020-01-22 16:30 ` Ethan Gardener
2020-01-22 16:47 ` hiro
2020-01-23 15:09 ` Ethan Gardener
[not found] ` <CAK0pxsHVpyae1+teTSOAFp=nBoq_r7-aKexh_X=hEDe7hUcReA@mail.gmail.com>
[not found] ` <CAK0pxsFDk=C_+37tKzU=U-TMQLTPcW6MOQ1sgKNBrYhWrj4Bwg@mail.gmail.com>
2020-01-23 18:12 ` Marshall Conover
2020-01-23 21:23 ` hiro
2020-01-23 22:42 ` Julius Schmidt
2020-01-24 0:39 ` Ethan Gardener
2020-01-24 0:44 ` Ethan Gardener
2020-01-23 23:50 ` Ethan Gardener
2020-01-24 0:59 ` Jeremy Jackins
2020-01-24 10:04 ` hiro
2020-01-21 8:37 ` [9front] Bounties Ethan Gardener
2020-01-22 17:04 ` Ori Bernstein [this message]
[not found] <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
2020-01-17 0:57 ` umbraticus
2020-01-05 7:06 Bounties Jens Staal
2020-01-16 18:05 ` [9front] Bounties Ethan Gardener
2020-01-17 0:47 ` sl
2020-01-16 18:51 ` Calvin Morrison
2020-01-16 19:35 ` Calvin Morrison
2020-01-16 23:03 ` Ethan Gardener
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=20200122090406.ed8c917dc4f88e511a1b85ef@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=kvik@a-b.xyz \
/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).