From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.1-1
Date: Wed, 11 Jan 2017 23:27:00 -0000 [thread overview]
Message-ID: <5876bf6d.69049d0a.6ccdd.3a1f@mx.google.com> (raw)
In-Reply-To: <23d48d46-3c93-3335-1859-71a2166c5c4f@SystematicSw.ab.ca>
On Wed, 11 Jan 2017 14:41:04, Brian Inglis wrote:
> I have not seen you provide any output from the locale command,
> or any mention of your Windows regional settings.
That is not how this works. I posit that this is a Cygwin issue, not a Steven
issue. I went back through all the posts of this thread and not a single person
has said:
"it works for me, I can enter non ASCII characters into interactive Bash via Alt
code or pasting. Must be your issue Steven"
once it has been proven it is my issue, I will jump through all those hoops you
are suggesting. Until then, it is pointless for me to run tests beyond what I
have already mentioned in my previous emails. This might very well by a Cygwin
issue and not a Steven issue, in which case that extra work will be a waste of
my time.
--
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-01-11 23:27 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 [this message]
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=5876bf6d.69049d0a.6ccdd.3a1f@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).