public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin@cygwin.com>
Subject: RE: [cygwin] Re: mintty phantom key presses
Date: Wed, 4 May 2022 14:04:20 -0400	[thread overview]
Message-ID: <16ac01d85fe1$61557360$24005a20$@pdinc.us> (raw)
In-Reply-To: <CAA=0bEMmB7UB-UGs9ZeTnjizKdin8=x+M0dg26c8vv1aYSECTg@mail.gmail.com>

> -----Original Message-----
> From: Eric Adams
> Sent: Wednesday, May 4, 2022 1:58 PM
> 
> On Tue, May 3, 2022 at 9:27 AM Jason Pyeron <jpyeron@pdinc.us> wrote:
> >
> > Does it happen on a fresh install (you can use another directory). I am interested because I have
> observed similar, but different, control code weirdness.
> >
> > v/r,
> > Jason
> >
> 
> Jason,
> I think I installed a fresh minimalist copy at C:\cygwin64TEST, went
> into the bin directory and invoked mintty.
> Within the new mintty, I started vi, and performed the vi insertion
> test. I did not find escape characters inserted.

Glad to hear there is a configuration that does not cause a problem.

> 
> I would try to note differences from my typical environment - a new
> binary directory / mintty invoked from the bin directory 

I usually copy the cygterm shortcut and update for the new root path and name - I am lazy.

> / running
> bash instead of tcsh / I think the home directory was the same / not
> all startup files were found or used / I felt very strange in this
> setup :) .

Start looking at input rc related things? 

Try to make the new match the old... testing along the way. diff -urw is your friend.

-Jason

--
Jason Pyeron  | Architect
PD Inc        | Certified SBA 8(a)
10 w 24th St  | Certified SBA HUBZone
Baltimore, MD | CAGE Code: 1WVR6
 
.mil: jason.j.pyeron.ctr@mail.mil
.com: jpyeron@pdinc.us
tel : 202-741-9397


      reply	other threads:[~2022-05-04 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 21:54 Eric Adams
2022-05-03  5:19 ` Thomas Wolff
2022-05-03 11:50   ` Eric Adams
2022-05-03 11:53     ` Thomas Wolff
2022-05-03 12:26       ` Eric Adams
2022-05-03 14:02         ` Thomas Wolff
2022-05-03 14:27           ` [cygwin] " Jason Pyeron
2022-05-04 17:57             ` Eric Adams
2022-05-04 18:04               ` Jason Pyeron [this message]

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='16ac01d85fe1$61557360$24005a20$@pdinc.us' \
    --to=jpyeron@pdinc.us \
    --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).