9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Eli Cohen <echoline@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] drawterm bug report
Date: Tue, 18 Feb 2020 12:20:22 -0800	[thread overview]
Message-ID: <CAHwi9bzFUff-bjk_SZpq3OasjjmW7toyAB7hY_C+jC3XKig2xQ@mail.gmail.com> (raw)
In-Reply-To: <708AA3D68C26498CFC501A962772BB03@a-b.xyz>

hiro -
I meant my "fix" is to simply bang on the ctrl key. everyone may not
realize to do that

On Tue, Feb 18, 2020 at 3:47 AM <kvik@a-b.xyz> wrote:
>
> > I imagine other people have noticed this.  sometimes when I
> > switch virtual workspaces on xfce4, drawterm's input gets
> > stuck somehow and when I type, control characters come out.
>
> Drawterm registers the keydown event, this trickles down to
> kbdfs, rio, and whatever, modifying their input states;
> then, drawterm's input focus is taken away by external
> forces, you release the key but drawterm doesn't ever get
> that keyup event, therefore everything continues to believe
> you are holding down that Ctrl key for life.
>
> I remember trying to work this out at some point, with the
> idea of tracking the keys being pressed and explicitly
> releasing them on focuslost event, or something like that.
>
> You can't do it wholesale or naively either, because for
> example Alt triggers the kbdfs compose mode that must be
> exited by pressing Alt again.



-- 
http://echoline.org


      reply	other threads:[~2020-02-18 20:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  9:31 Eli Cohen
2020-02-18 11:25 ` [9front] " hiro
2020-02-18 11:46 ` kvik
2020-02-18 20:20   ` Eli Cohen [this message]

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=CAHwi9bzFUff-bjk_SZpq3OasjjmW7toyAB7hY_C+jC3XKig2xQ@mail.gmail.com \
    --to=echoline@gmail.com \
    --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).