public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dominic Bragge <dom@benelec.com.au>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Sudden loss of "e" key in cygwin only - Fixed
Date: Tue, 06 Aug 2019 04:27:00 -0000	[thread overview]
Message-ID: <aeb6a42de6ae4014a132555d18ad74de@benelec.com.au> (raw)

FYI
It seems a minor change (two Echo statements) in my .inputrc caused the problems
I'm not sure why.

All ok now

(Using minty.... problem was still there when I tried bash)

Dom



-----Original Message-----
From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> On Behalf Of Dominic Bragge
Sent: Tuesday, 6 August 2019 12:32 PM
To: cygwin@cygwin.com
Subject: Sudden loss of "e" key in cygwin only

I'm new on the list today
I use generally use Cygwin for minimalist trawling through ascii dumps of databases using combos of grep awk printf etc


I cannot type "grep" on cmd line in cygwin anymore as of this morning!


It seems I have lost the lowercase "e" key. Uppercase works. All other keys seems to work.
All keys work in windows (on same computer).

Any clues anyone?


Thanking you kindly
Dom
Sydney, Australia


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2019-08-06  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  4:27 Dominic Bragge [this message]
2019-08-06 17:08 ` steve shepard

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=aeb6a42de6ae4014a132555d18ad74de@benelec.com.au \
    --to=dom@benelec.com.au \
    --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).