From: "José Miguel Sánchez García" <soy.jmi2k@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Mouse clipping patch
Date: Tue, 13 Jul 2021 17:34:44 +0200 [thread overview]
Message-ID: <CAA85C84kc46zYNxTJdzfu4V9aU+8ipyKdD8u_Bgo4UDcUzgaUg@mail.gmail.com> (raw)
In-Reply-To: <CAA85C84BsFY97VYJZjMufRZmPcBmEVvVZ+EsMxyDkGfPJELbpw@mail.gmail.com>
Thinking about it, seems like screenlock is the odd one here: I can't
think about other use case which would require that level of control
over the mouse. Ideally, a system which could "navigate up" the stack
of rio (unfocusing them from their container) would be a good idea to
both escape the clip prison and also to open the door to future
keyboard-based interactions in an elegant way. If that didn't get in
the way of screenlock, I would undoubtely implement that.
On Tue, Jul 13, 2021 at 5:09 PM José Miguel Sánchez García
<soy.jmi2k@gmail.com> wrote:
>
> We have a problem too: there are programs which we don't want to
> release their grab EVER. screenlock would be pretty lame if you could
> just "ungrab" the mouse.
>
> I think that different programs have different needs, so maybe
> convention is enough? Follow it, unless it makes no sense...
>
> On Tue, Jul 13, 2021 at 5:07 PM hiro <23hiro@gmail.com> wrote:
> >
> > no, that is never a problem as rio forwards the keyboard commands to
> > the relevant selected subprocess (scrollock, DEL and ESC keys for
> > example).
> >
> > On 7/13/21, Stuart Morrow <morrow.stuart@gmail.com> wrote:
> > > On 13/07/2021, José Miguel Sánchez García <soy.jmi2k@gmail.com> wrote:
> > >> There is none, but that's a different issue (it could be easily solved
> > >> if rio provided an "uncurrent" key or an alt-tab-like key.
> > >
> > > I can make the case, without appealing to personal preference, that
> > > keyboard-driven wm doesn't belong in Plan 9: we nest window managers.
> > > How do you get keyboard commands into the inner rio?
> > >
next prev parent reply other threads:[~2021-07-13 16:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 19:50 José Miguel Sánchez García
2021-07-13 2:36 ` ori
2021-07-13 2:45 ` ori
2021-07-13 14:03 ` Stuart Morrow
2021-08-11 0:56 ` Stuart Morrow
2021-07-13 3:14 ` José Miguel Sánchez García
2021-07-13 8:25 ` hiro
2021-07-13 10:27 ` José Miguel Sánchez García
2021-07-13 14:05 ` Stuart Morrow
[not found] ` <CAFSF3XPhDeKiKXdsL0Abnderm45Uc2GCPYsi6ygSaBkf7gDBmA@mail.gmail.com>
2021-07-13 15:09 ` José Miguel Sánchez García
2021-07-13 15:34 ` José Miguel Sánchez García [this message]
2021-07-14 12:04 ` Stuart Morrow
2021-07-15 2:06 ` Xiao-Yong Jin
2021-07-13 15:11 ` Stuart Morrow
2021-07-13 16:16 ` José Miguel Sánchez García
2021-07-13 16:27 ` Stuart Morrow
2021-07-13 17:42 ` José Miguel Sánchez García
2021-07-13 21:20 ` hiro
2021-07-13 21:57 ` ori
2021-07-14 11:55 ` Stuart Morrow
2021-07-13 17:26 ` Xiao-Yong Jin
2021-07-13 17:45 ` Stuart Morrow
2021-07-13 18:29 ` José Miguel Sánchez García
2021-07-13 21:32 ` hiro
2021-07-13 21:22 ` Benjamin Purcell
2021-07-13 16:21 ` hiro
2021-07-13 16:29 ` ori
2021-07-14 8:42 ` hiro
2021-07-14 11:52 ` Stuart Morrow
2021-07-14 12:17 ` hiro
2021-07-15 3:13 ` ori
2021-07-14 12:53 ` José Miguel Sánchez García
2021-07-15 7:36 ` hiro
2021-07-14 14:26 ` ori
2021-07-13 15:27 ` kvik
2021-07-13 16:28 ` ori
2021-07-13 12:00 ` José Miguel Sánchez García
2021-07-13 12:43 ` kvik
2021-07-13 13:36 ` hiro
2021-07-13 13:40 ` hiro
2021-07-14 22:57 ` ori
2021-07-15 7:40 ` hiro
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=CAA85C84kc46zYNxTJdzfu4V9aU+8ipyKdD8u_Bgo4UDcUzgaUg@mail.gmail.com \
--to=soy.jmi2k@gmail.com \
--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).