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 B48D5222FA for ; Sun, 30 Jun 2024 18:54:39 +0200 (CEST) Received: from mail.posixcafe.org ([45.76.19.58]) by 9front; Sun Jun 30 12:53:50 -0400 2024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posixcafe.org; s=20200506; t=1719766390; 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=NS6LS9Mrrcgfa7t7yOBN0/isdGXDa4f8ZmXJClrv34Y=; b=ftMwc9WkIC9SdHAbNUEmiSaSWjICNfvwifn5XqHBEvxOa2gkWRI7NtbnbFq1D4YQKsgJ8V wqt7/yweL1u6+DUWvmW13+COcDW3sOtmoNFadXghw+z6aOTms5/NIo8AwxNqq7s8gUWZ2h EkJgxEUEhKsyT1AxpsCMw+O78FfihCQ= Received: from [192.168.168.200] ( [207.45.82.38]) by mail.posixcafe.org (OpenSMTPD) with ESMTPSA id 14984b35 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO) for <9front@9front.org>; Sun, 30 Jun 2024 11:53:09 -0500 (CDT) Message-ID: Date: Sun, 30 Jun 2024 11:53:46 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: 9front@9front.org References: <0e48ff1e-f33e-49ed-b40c-ea2f442e4c56@posixcafe.org> Content-Language: en-US From: Jacob Moody In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: progressive realtime-aware XMPP CSS extension Subject: Re: [9front] [PATCH] Fix shift release events in X11 drawterm with shift:both_capslock xmodmap option Reply-To: 9front@9front.org Precedence: bulk On 6/29/24 06:16, Timothy Robert Bednarzyk wrote: >> 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 mouse 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. > Sure rio is a standin for whatever "main" graphical application you're running. I just want to avoid oversharing in the comment to raise more questions then it answers. I thought that the later portions of the comment can be safely extrapolated from the cause of the bug as is described, so I feel it's filler. This is your work though not mine so I won't die no this hill over some comment bikeshedding. Let me know what you would like. Thanks, moody