From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=1.0 required=5.0 tests=DATE_IN_PAST_03_06,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 8392 invoked from network); 15 Jul 2021 04:47:37 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 15 Jul 2021 04:47:37 -0000 Received: from mail-vk1-f172.google.com ([209.85.221.172]) by 1ess; Tue Jul 13 23:10:06 -0400 2021 Received: by mail-vk1-f172.google.com with SMTP id bb26so157464vkb.10 for <9front@9front.org>; Tue, 13 Jul 2021 20:09:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=R1rjpXYuHVaWzQIjzha8NRBKi4MwIBktDlQU9HmsCFM=; b=AjNbMSTJ4PfaKFr3Q8292Vky67Ko92GYz/Zgn/Bx9d7WHbrSzvqWAEm5pV/iVWrowE /wFrnL9d8DatQUC32FsUElh7ZEm6M/Htza+lLBOWLW1ORmAK4KP+lNvAyxqQoVRSe8lL rEZBwJzzcdv5iAqlEx3Pz8+tMevJlDRaJF3ujeo4L19sGrn1yp4wxqiToBx3kgotCEp2 ngdkP/ALaYrQVbF7OQRGl8y1kJk3zhJFemjL2XADR5bj89Cd3CvDisQpvEa9qHlyZGns PrwmUiyMfThTGd+onbUEtlmndobK4DvEEeAk3aK8VAHJ4AsZnZm0rHJu5hpP7SIYULVp OROg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=R1rjpXYuHVaWzQIjzha8NRBKi4MwIBktDlQU9HmsCFM=; b=StxADwNfL8hVteoTjC2HRIrizvYBOlHAld/VGCWBGrmHD+dXp0tmDtu0XB/ri9lzLa SmXvQGxNisuu0/zCs2osthJC9khZY5DbyFnapEYTs9KI+F+gnKiSBdFn2aP7CRJpfxAG cNSBBYBeuG38ywIq1WiSJeOZVlOEjDQCE010TEdYkwhNq4g9drqxc9ab2soJCZAyO+ij Hk1eTT/zUQY2In59vzTBHO9EK3FvLIUhCA8HMohvHfrGJj4LUkWibsqA7Nd3Lxf3GEtN sbA8ZOs0jZGwgDBiThPwZDbdIq6U8VRQ+6Z4MeIWppi74kliIIWbFvphw14ysWaIktfC HLCg== X-Gm-Message-State: AOAM530Tg7kSk4dMLfndOgZtZaoxh7AzlWu6GfUFzbPeB7GXdrqpba38 i20P5hAOFHln2INRKusqnKieWSF4Tw19r/t+gt/nCuRh X-Google-Smtp-Source: ABdhPJw1O7KbzRAPuLt11uPVgLKrT2a7wgbG41vxhdNGkRQTtitNeNvnFcAjwiCXIfFCVgKpaGle3WZ0J4GjuT/VbeM= X-Received: by 2002:a17:902:8e88:b029:11e:b703:83f1 with SMTP id bg8-20020a1709028e88b029011eb70383f1mr4897620plb.79.1626211213024; Tue, 13 Jul 2021 14:20:13 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6a20:a002:b029:1e:dcb9:6f96 with HTTP; Tue, 13 Jul 2021 14:20:12 -0700 (PDT) In-Reply-To: References: <8CE29EA89CBA8F74C1D4D8EEF2528473@eigenstate.org> From: hiro <23hiro@gmail.com> Date: Tue, 13 Jul 2021 23:20:12 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: agile generic service full-stack service Subject: Re: [9front] Mouse clipping patch Reply-To: 9front@9front.org Precedence: bulk so again, what is the problem with just using ESC (hold mode) for this? On 7/13/21, Jos=C3=A9 Miguel S=C3=A1nchez Garc=C3=ADa = wrote: > The concept of focus itself is a rio invention, so it's natural that > the way of giving it up is also rio-specific. > > Again: mouse comes with two sets of inputs: the pointer location and > the buttons. The pointer location can decide the receiver end of the > mouse events (well, not quite in the case of rio, because its focus > doesn't follow the mouse, but you get the idea). On the other hand, > keyboard can't "point" to where the input should be processed, so the > concept of a "current window" fills that hole. It's natural that, if > we have invented a synthetic way of "pointing to" a window with the > keyboard (focus), we should also have a way of "pointing out" of a > window with the keyboard (a "uncurrent" key). > > Maybe I'm overthinking it, but that's how I feel about it. Needless to > say, feel free to offer any other alternative to escape the mouse > clip. Feedback is very welcome :) > > On Tue, Jul 13, 2021 at 7:32 PM Stuart Morrow > wrote: >> >> > Innermost-focused rio gets the control, with a key for "giving up" the >> > focus (going then a "level" up in the stack) is what i propose. >> >> But it's so _untransparent_ >