From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: xterm tab key (temporarily) locks keyboard
Date: Mon, 19 Oct 2020 10:49:15 +0100 [thread overview]
Message-ID: <CA+kUOannAixTFc0_8AHwWmHgnH5e6HPTUzyx_C9-79FwmeLv2g@mail.gmail.com> (raw)
In-Reply-To: <75d0fc04-8f88-9533-4997-ced1146f6e6d@SystematicSw.ab.ca>
On Sun, 18 Oct 2020 at 19:23, Brian Inglis wrote:
>
> On 2020-10-18 12:07, Frank Eske via Cygwin 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?
>
> Bash command completion is searching for commands to display - you will
> eventually get asked if you want to "Display all 4587 possibilities? (y or n)"
> (or similar number) after it has loaded all executable names from all
> directories in your PATH!
There are a few things that can make this particularly painful:
- Your Cygwin environment inheriting a large PATH from Windows, so it
needs to search through a lot of directories.
- The PATH containing network shares, especially if some of those
network shares are relatively slow.
You can check what's currently in your PATH by just running `echo
$PATH`. There's lots of different ways of resolving this, but probably
the easiest is to reset your PATH by adding something like `export
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin` to
your ~/.bashrc file.
next prev parent reply other threads:[~2020-10-19 9:49 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 [this message]
2020-10-21 17:45 ` Frank Eske
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=CA+kUOannAixTFc0_8AHwWmHgnH5e6HPTUzyx_C9-79FwmeLv2g@mail.gmail.com \
--to=adam@dinwoodie.org \
--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).