public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Emacs and CTRL key problems using Cygwin 3.0.3
Date: Fri, 15 Mar 2019 11:29:00 -0000	[thread overview]
Message-ID: <776541bb-899a-c249-a8ec-e3c85f1bbf91@towo.net> (raw)
In-Reply-To: <CAH8yC8m1X1T33Ru7h3mONLDhnZetES8rmF_FenMxqcTpyC5CQA@mail.gmail.com>

Am 15.03.2019 um 12:16 schrieb Jeffrey Walton:
> On Fri, Mar 15, 2019 at 5:59 AM Thomas Wolff <towo@towo.net> wrote:
>> Am 15.03.2019 um 07:29 schrieb Jeffrey Walton:
>>> Hi Everyone,
>>>
>>> I just upgraded to Cygwin 3.0.3. 3.0.3 was an in-place upgrade over
>>> top the previous version. I don't recall the previous version.
>>>
>>> I used Cygwin x86_64 flavor and SSH'd into a Linux box. I opened a
>>> text file with emacs and tried to delete a line with CTRL+K. Notice
>>> the '5;5u' where the delete was supposed to occur:
>>>
>>>       IS_APK=$(command -v apk 2>/dev/null | grep -v "^no " | wc -l)
>>>
>>>       5;5u5;5u5;5u
>>>
>>>       if [ "$IS_DNF" -ne 0 ]; then
>>>
>>> Formerly emacs worked as expected.
>> Fixed with mintty 2.9.8.
> I just updated, and saw mintty was the only package. But I am still seeing the issue.
Sure you're running mintty 2.9.8 when you again see the issue? Please 
check in Options - About.

--
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-03-15 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  6:30 Jeffrey Walton
2019-03-15  9:59 ` Thomas Wolff
2019-03-15 11:17   ` Jeffrey Walton
2019-03-15 11:29     ` Thomas Wolff [this message]
2019-03-15 16:05     ` Andrey Repin
2019-03-16  5:37       ` Jeffrey Walton
2019-03-17  5:06 ` Jeffrey Walton

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=776541bb-899a-c249-a8ec-e3c85f1bbf91@towo.net \
    --to=towo@towo.net \
    --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).