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=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10532 invoked from network); 27 Aug 2022 13:33:49 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 27 Aug 2022 13:33:49 -0000 Received: from mail-vk1-f181.google.com ([209.85.221.181]) by 9front; Sat Aug 27 09:30:24 -0400 2022 Received: by mail-vk1-f181.google.com with SMTP id q14so1858151vke.9 for <9front@9front.org>; Sat, 27 Aug 2022 06:30:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:references:in-reply-to:mime-version :from:to:cc; bh=+5mmrMWFmkB/epjGDQwo1qwPstJTQ7GzMbJNmBwApZA=; b=JNRouAUnZ6N7kdrtgnI0N7mDHWaDkyuT6eAk2GOLVZanNqwHqTZPlvG2Q8P3wPp0Yv mzxe/4K/+iaDSfqemvouk/YmRuZnSILhTMEY7xAkRC8Xzsx8cRXCkpMqFFM6KdkE3Ps9 T33sB1crHIq+1YDgevZERtoI4xWE1vtxuZSWtcQ4Pbjg7t/YaRBjgSWpvx2ZHp1Qn81q 3V5c6bCMqF/V/S5nxtNqzFsWwzd9BnSLhGLlWazxoXMApufIUgouEO+vrR2aiRIsb3hu zxI7L8l1h3T9SsdMLQJh8CSsH2SoNewdojsrEEZnllRWbpC8vWFddnPPcXmK8TWy0dMF tXvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:references:in-reply-to:mime-version :x-gm-message-state:from:to:cc; bh=+5mmrMWFmkB/epjGDQwo1qwPstJTQ7GzMbJNmBwApZA=; b=c3J1jo+BVYMqdrMT2tVBPfh7LHNrlFYxr0k+hayfRuf8WDRJ3RhxZhKZ9KbU8ZbKLL tqr0DKPAdoFopPd55hCMHp6OHXDRhm65TyWEqnvhdhv6iUQtv2fa5DGCgjE2vW/9vwmp /j8xiZqpk/W0IjmQLlukqwqieYMDgt1URKTMy0shysvGJTN1AcUNkSR3ZFYvV+4r+eI9 t6UkzVo/GIkk4eHIMQ8MqCigTr5HyjPLZ7H4rBwsw8ANr+jvLOWrCyzMCi+6uigoXY4U VLSLnV+49T9iqQZFCMI85BfCMzEfI37MkkFK4+RO185iyRxvFoF1fwGmmCBvidPBNb4S 4oeQ== X-Gm-Message-State: ACgBeo2ah+RfGSHnK4kdHbrnjl+yQN+A2EYN8t7UVf4jPyBuGOX9UMdr MK+z/dEr9FF0z3cKls3hVgBWJDufF+DMHXMZHGUpU0Bl5HE= X-Google-Smtp-Source: AA6agR6SbsV8njwzkRdCVTuForGoZiPUr5cnBSEcdJR2umgxyMl3LmHVcJwXV2jbc8HNqS3S78YxDLRfJqoxlM2xWtI= X-Received: by 2002:a1f:a78f:0:b0:394:32b4:78ac with SMTP id q137-20020a1fa78f000000b0039432b478acmr301147vke.29.1661607021187; Sat, 27 Aug 2022 06:30:21 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ab0:6056:0:0:0:0:0 with HTTP; Sat, 27 Aug 2022 06:30:20 -0700 (PDT) In-Reply-To: <6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org> References: <6096F7A2A4FAE4D19DAB0F94D4F28672@eigenstate.org> From: hiro <23hiro@gmail.com> Date: Sat, 27 Aug 2022 15:30:20 +0200 Message-ID: To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: leveraged responsive ACPI over ORM GPU CMS NoSQL control Subject: Re: [9front] [PATCH] programmable menus for rio Reply-To: 9front@9front.org Precedence: bulk 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.