From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 544FE23F2C for ; Sat, 29 Jun 2024 13:18:35 +0200 (CEST) Received: from out-188.mta0.migadu.com ([91.218.175.188]) by 9front; Sat Jun 29 07:16:54 -0400 2024 X-Envelope-To: 9front@9front.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=trbsw.dev; s=key1; t=1719659812; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VEUywQYeaF2315laTgmXiEcTOQ9ayLqNtRq4wTYQwrk=; b=y0zeaCgSyTtGs0tp/IN8EKcWUL5xBs4reYoJr+keYVgB83FkafOVNJ95ml7EZ1C1q+ILIt y4XrdjjYKRvPicbNm8eRTZ8vcA/UQ3GyJk1mjF82WTcUsZ8LIl+vanh/9UIgy+R0d1+nok P8MUR/t0aJVDcn2hciC2POKUB7Lmcso= Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Sat, 29 Jun 2024 07:16:48 -0400 Message-Id: X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Timothy Robert Bednarzyk" To: <9front@9front.org> References: <0e48ff1e-f33e-49ed-b40c-ea2f442e4c56@posixcafe.org> In-Reply-To: <0e48ff1e-f33e-49ed-b40c-ea2f442e4c56@posixcafe.org> X-Migadu-Flow: FLOW_OUT List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: progressive template package ACPI descriptor pipelining layer Subject: Re: [9front] [PATCH] Fix shift release events in X11 drawterm with shift:both_capslock xmodmap option Reply-To: 9front@9front.org Precedence: bulk > Seems reasonable to me. Thanks for debugging this. > My only suggestion would be to axe the "Not having this causes the mouse = ...". > What it causes is the shift key to be held down, which then causes the mo= use button swapping. > Drawterm itself isn't doing that bit, it's rio. While it is true that it technically isn't drawterm itself causing that to happen, it also isn't _just_ rio---holding the shift key after starting acme directly (instead of starting rio and then running acme inside a rio window) still swaps the mouse buttons. Given that I wasn't also experiencing a problem where everything I typed was capitalized as if it thought that I was just constantly holding down the shift key, I was only trying to provide context to what can actually be observed without specially handling "caps lock" key releases. That being said, I'm perfectly fine with either rephrasing or entirely axing that. -- trb