public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1
Date: Wed, 11 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <58757597.8440ca0a.2df89.9dc4@mx.google.com> (raw)
In-Reply-To: <62da2733-e302-bc19-66dc-1721f3349c82@SystematicSw.ab.ca>

On Tue, 10 Jan 2017 13:08:30, Brian Inglis wrote:
> Alt-numpad-decimal e.g. Alt234 depends on the console codepage selected.

I tested this on Windows 7 in a pristine virtual machine, and cmd.exe passes
just fine, even with code page 437 and crappy raster font. Meanwhile bash.exe
fails.

> Mintty selection of Options/Text/Locale and Character set UTF-8 or cmd 
> chcp 65001 selects Unicode. 

No one said anything about Mintty. This is about bash.exe, launched by itself
or via Cygwin.bat

> Alt-numpad-+-hex (on regular keys) allows hex unicode input e.g. 
> Alt+3a9 if the font supports the character.

No one said anything about hex input.

> Free text fonts which support Unicode character emojis are updated 
> regularly. 
> Look for Cygwin packages matching ...font... containing Truetype or 
> Opentype fonts, and just copy them to Windows/Fonts e.g.

A font does not need to be installed. Raster, Consolas and Lucida all work
already through cmd.exe.

I do appreciate your response, but all you have done here is thrown a bunch of
guesses at the wall hoping something would stick. It would be a better use of
everyones time if you actually tested your suggestions before posting them.


--
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:[~2017-01-11  0:00 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 [this message]
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
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=58757597.8440ca0a.2df89.9dc4@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).