public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Frank Eske <fne.bugzilla@gmail.com>
To: cygwin@cygwin.com
Subject: Re: xterm tab key (temporarily) locks keyboard
Date: Wed, 21 Oct 2020 13:45:32 -0400	[thread overview]
Message-ID: <CAETRzVLbWkvtpb9rpc5WVLh-4k6aA2Zg_90N+uxnX7aKCPnZ=g@mail.gmail.com> (raw)
In-Reply-To: <CAETRzVL2Orhq0xStoxZCVsuMnbs_wmBX8cJAAjDu-+9Yo4NjWA@mail.gmail.com>

There may be some other key or key combination on the left side of the
keyboard that's doing this also. While the tab key can reproducibly cause
it, some other key combination might also.

Since my bash version is Jan 27, 2017 and none of my .bash scripts have
changed recently, xterm (Sep 20, 2020) seems like the most likely culprit.
I did create a .fonts file for experimentation which is just now removed.
(It's too early to tell whether that somehow created this problem.)

On Sun, Oct 18, 2020 at 2:07 PM Frank Eske <fne.bugzilla@gmail.com> wrote:

> If the tab key is entered as the first character running the bash shell on
> an xterm terminal, the keyboard temporarily locks. Control-C writes ^C but
> doesn't unlock it. This doesn't happen on Fedora. It also doesn't lock if a
> space is typed first.
>
> This occurs whether or not the xterm console is in an X environment.
>
> For some reason I seem to accidentally do this a lot more often than I'd
> like, so it's a real nuisance. I checked this mailing list for the last
> four months and couldn't find " tab" or a useful "tab ", I find it
> difficult to believe that I'm the first to see this, so maybe there's
> something I changed that's making this happen. Any advice on what that
> might be?
>
>
>

  parent reply	other threads:[~2020-10-21 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18 18:07 Frank Eske
2020-10-18 18:23 ` Brian Inglis
2020-10-19  9:49   ` Adam Dinwoodie
2020-10-21 17:45 ` Frank Eske [this message]
2020-10-21 17:55   ` Thomas Wolff

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='CAETRzVLbWkvtpb9rpc5WVLh-4k6aA2Zg_90N+uxnX7aKCPnZ=g@mail.gmail.com' \
    --to=fne.bugzilla@gmail.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).