public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Possible phantom control-key state moving from windows to cygwin
Date: Wed, 2 Mar 2022 10:46:26 +0900	[thread overview]
Message-ID: <20220302104626.ed3450432f701308f6c2b248@nifty.ne.jp> (raw)
In-Reply-To: <CAA=0bEOzHw8-KxqC_hEhP-W5C7Y3aWrzubCM62rfWEAUtC65yA@mail.gmail.com>

On Tue, 1 Mar 2022 19:17:50 -0600
Eric Adams wrote:
> Hi, and thanks for all the wonderful work.
> 
> I have noticed "recently" that when I move from using a graphical
> windows application (e.g. VeraCrypt) to typing in a cygwin mintty
> window, the first character typed may think that the control key is
> active. This is often not a problem, unless the first character typed
> is a "d". I'm running tcsh as my shell.
> 
> Let me know if I can add more information.

Is the problem reproducible with other apps than VeraCrypt?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2022-03-02  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-02  1:17 Eric Adams
2022-03-02  1:46 ` Takashi Yano [this message]
2022-03-02  2:36   ` Eric Adams

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=20220302104626.ed3450432f701308f6c2b248@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).