From: "Ken Reek" <kenreek1@gmail.com>
To: <cygwin@cygwin.com>
Subject: RE: mintty will not accept the letter "e"
Date: Sun, 30 Aug 2020 07:02:27 -0600 [thread overview]
Message-ID: <01b301d67ecd$d096d670$71c48350$@gmail.com> (raw)
In-Reply-To: <d5daaaa7-72b3-faf1-7244-7dea2380f7fb@towo.net>
Found the problem! One of the FAQs instructed me to add the command
set completion-ignore-case on
to the .inputrc file. Seeing a "set" command I thought this file was similar
to .bashrc so I added the command
echo .inputrc
to the file (so I could be sure it was being read). After reading the bash
manual while awake at 2 this morning I found that the Readline syntax is
quite different. I think this command was being mis-parsed as a key
binding.
Removing the offending line fixed the problem. Thanks to all who responded
with suggestions.
- Ken
-----Original Message-----
From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Thomas Wolff
Sent: Saturday, August 29, 2020 5:04 PM
To: cygwin@cygwin.com
Subject: Re: mintty will not accept the letter "e"
Am 30.08.2020 um 00:42 schrieb Ken Reek via Cygwin:
> Hi, all.
>
> All of the sudden, mintty won't accept a lower case "e" -- it just
> dings when I try to type one. Upper case "E" is fine, as are all the
> other letters. I'm no mintty expert, but I think the e key might have
> been remapped somehow.
>
> Any ideas on how I can fix this? I've killed mintty and started it
> again, and also rebooted my machine, to no avail. I'm on Windows 10.
> Thanks for any help!
What a strange report - there is no way mintty could be causing such an
effect. Maybe you've somehow changed your keyboard mapping? What about other
letters? Other applications? Windows cmd console?
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2020-08-30 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-29 22:42 Ken Reek
2020-08-29 23:03 ` Thomas Wolff
2020-08-30 1:09 ` Ken Reek
2020-08-30 1:14 ` Yasuhiro KIMURA
2020-08-30 2:14 ` Ken Reek
2020-08-30 5:18 ` Thomas Wolff
2020-08-30 13:02 ` Ken Reek [this message]
2020-08-30 8:47 ` Vlado
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='01b301d67ecd$d096d670$71c48350$@gmail.com' \
--to=kenreek1@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).