public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1
Date: Wed, 11 Jan 2017 01:35:00 -0000	[thread overview]
Message-ID: <CAOC2fq9PBOuV63d6aSjuzFe3p_FBiESv1PZC+9baxbGiWi6zQw@mail.gmail.com> (raw)
In-Reply-To: <58742d35.43029d0a.29fa1.0df9@mx.google.com>

On Mon, Jan 9, 2017 at 4:39 PM, Steven Penny <svnpenn@gmail.com> wrote:
> It looks like fixing this may have caused another issue. Example test:
>
> With cmd.exe, you can type Alt 234 and it produces
> GREEK CAPITAL LETTER OMEGA U+03A9. However with Cygwin via Cygwin.bat it yields
> nothing. Non ASCII characters can be read from scripts, but they cannot be
> entered interactively.
>
> They cannot be pasted either; pasting some words will remove all non ASCII
> characters.
>

My cygwin 32-bit install has not been updated for a while. When I do
ALT234 with numeric pad keys and numlock on, from bash directly
running under cmd.exe, I get :\251 at first (colon backslash 251) and
then when I hit enter for the command, I get a beep.
If I do the ALT234 with numeric pad and numlock in CMD.exe I do get
what looks like a capital omega. So a months old bash does not respond
well to this ALT numpad stuff.

My information supports the judgement that weird behavior in this area
was introduced a while ago.

For comparison only, If I do ALT234 with mintty running bash, I get
neither the :\251 nor capital omega, I get lower case e with
circumflex.


>c:\cygwin\bin\bash --version
GNU bash, version 4.3.42(4)-release (i686-pc-cygwin)

--
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

  parent reply	other threads:[~2017-01-11  1:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  0:39 Steven Penny
2017-01-10 20:08 ` Brian Inglis
2017-01-11  0:00   ` Steven Penny
2017-01-11  6:51     ` Brian Inglis
2017-01-11 12:52       ` Steven Penny
2017-01-11 17:54         ` Brian Inglis
2017-01-11 19:37           ` Steven Penny
2017-01-11 20:41             ` Eliot Moss
2017-01-11 23:19               ` Steven Penny
2017-01-11 23:22                 ` Eliot Moss
2017-01-11 23:29                   ` Steven Penny
2017-01-11 21:41             ` Brian Inglis
2017-01-11 23:27               ` Steven Penny
2017-01-11  1:35 ` Michael Enright [this message]
2017-01-12 14:23 ` John Hein
2017-01-12 18:48 ` David Macek
  -- strict thread matches above, loose matches on Subject: below --
2016-12-18  8:43 Corinna Vinschen
2016-12-21 19:10 ` David Stacey
2016-12-21 20:38   ` 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=CAOC2fq9PBOuV63d6aSjuzFe3p_FBiESv1PZC+9baxbGiWi6zQw@mail.gmail.com \
    --to=mike@kmcardiff.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).