public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.7.0-0.1
Date: Fri, 03 Feb 2017 09:14:00 -0000	[thread overview]
Message-ID: <20170203091407.GO8905@calimero.vinschen.de> (raw)
In-Reply-To: <20170203083947.GN8905@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]

On Feb  3 09:39, Corinna Vinschen wrote:
> On Feb  2 17:50, Steven Penny wrote:
> > On Thu, 02 Feb 2017 17:37:35, Steven Penny wrote:
> > > Ok, I found that if I install cygwin-2.7.0 and libreadline7-7.0.1-2 then this
> > > works as exepcted. I didnt realize libreadline7-7.0.1-2 was still in test
> > > status. However I thought that the Cygwin DLL update meant that the readline
> > > hack was not necessary? Please advise.
> > 
> > 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.
> 
> Cygwin 2.7.0:
> 
> Works in tcsh and dash, even with chcp 65001.  Does not work with
> bash for some reason in cp 65001.
> 
> Why are you switching to cp 65001, btw?  It's completely unnecessary
> for utf-8 to work in the Windows console.  Just stick to the default.

I wonder if that's a problem in the Windows console.  In theory the
console codepage should have no influence on Cygwin.  Codepages only
should influence non-Unicode aware applications, but console I/O in
Cygwin is using Unicode throughout.

Weird.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2017-02-03  9:14 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 [this message]
2017-03-19  4:23                 ` Steven Penny
2017-03-20 19:06                   ` cyg Simple
2017-03-20 22:49                     ` Steven Penny
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=20170203091407.GO8905@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).