From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.7.0-0.1
Date: Mon, 20 Mar 2017 22:49:00 -0000 [thread overview]
Message-ID: <58d05c60.8441ca0a.713c7.92eb@mx.google.com> (raw)
In-Reply-To: <be3ac5a3-741a-ce02-8ff5-14955d9590da@gmail.com>
On Mon, 20 Mar 2017 15:06:26, cyg Simple wrote:
> This really isn't a Cygwin issue as I see it. What occurs if you run
> your mingw32.exe in a CMD command window? This may be a mintty issue
> but certainly not because of Cygwin itself. But even the mintty case is
> dependent on the results you see in CMD.
Wrong. Somewhere between the Cygwin, Bash and Readline this got messed up:
On Thu, 02 Feb 2017 17:50:55, Steven Penny wrote:
> Correction again, this nightmare keeps getting worse. Using this test:
> %ö
> Pasting fails for every recent combination. The only fix I found was falling
> back to bash-4.3.48 and libreadline7-6.3.8. Please fix this, starting to make my
> head hurt.
http://cygwin.com/ml/cygwin/2017-02/msg00031.html
--
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
next prev parent reply other threads:[~2017-03-20 22:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 15:45 Corinna Vinschen
2017-02-02 3:19 ` Steven Penny
2017-02-02 5:21 ` Steven Penny
2017-02-02 12:50 ` Steven Penny
2017-02-02 13:30 ` Corinna Vinschen
2017-02-03 0:08 ` Steven Penny
2017-02-03 1:37 ` Steven Penny
2017-02-03 1:50 ` Steven Penny
2017-02-03 8:39 ` Corinna Vinschen
2017-02-03 9:10 ` Houder
2017-02-03 9:30 ` Houder
2017-02-03 12:49 ` Steven Penny
2017-02-03 17:43 ` Houder
2017-02-03 9:14 ` Corinna Vinschen
2017-03-19 4:23 ` Steven Penny
2017-03-20 19:06 ` cyg Simple
2017-03-20 22:49 ` Steven Penny [this message]
2017-03-22 20:17 ` cyg Simple
2017-03-22 21:07 ` Steven Penny
2017-02-02 13:05 ` Corinna Vinschen
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=58d05c60.8441ca0a.713c7.92eb@mx.google.com \
--to=svnpenn@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).