9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Timothy Robert Bednarzyk" <mail@trbsw.dev>
To: <9front@9front.org>
Subject: Re: [9front] [PATCH] Fix shift release events in X11 drawterm with shift:both_capslock xmodmap option
Date: Sat, 29 Jun 2024 07:16:48 -0400	[thread overview]
Message-ID: <D2CGIXPYRVDT.1CMHBD42ODOBC@trbsw.dev> (raw)
In-Reply-To: <0e48ff1e-f33e-49ed-b40c-ea2f442e4c56@posixcafe.org>

> 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.

--
trb

  reply	other threads:[~2024-06-29 11:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28 23:53 Timothy Robert Bednarzyk
2024-06-29  0:30 ` Jacob Moody
2024-06-29 11:16   ` Timothy Robert Bednarzyk [this message]
2024-06-30 16:53     ` Jacob Moody
2024-06-30 19:22       ` Timothy Robert Bednarzyk
2024-06-29 16:31 ` hiro
2024-06-29 17:19   ` Timothy Robert Bednarzyk
2024-06-30 16:39     ` hiro
2024-06-30 19:08       ` Timothy Robert Bednarzyk

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=D2CGIXPYRVDT.1CMHBD42ODOBC@trbsw.dev \
    --to=mail@trbsw.dev \
    --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).