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: libreadline7-7.0.1-1, libreadline-devel-7.0.1-1, bash-4.4.5-1
Date: Wed, 18 Jan 2017 03:55:00 -0000	[thread overview]
Message-ID: <587ee723.e1039d0a.48332.ec2d@mx.google.com> (raw)
In-Reply-To: <22d8cd67-3a5a-9f7f-9e4a-eb0a43bd5b2c@redhat.com>

On Tue, 17 Jan 2017 20:08:17, Eric Blake wrote:
> [again, your email client likes to break threading, so I nearly missed
> this one]

Sorry about that, I wrote my own client so that I could reply without
subscribing:

http://github.com/svnpenn/a/blob/master/etc/mailing-list.awk

I switched the "In-Reply-To" header to "References", hopefully that will fix it.

> Are you building readline from source each step of the bisection?

Yes.

> are you applying all the downstream cygwin patches each build, or just using
> the stock upstream sources?

The latter.

> Normally, I _don't_ run anything under cmd.exe (all my use of cygwin is
> under mintty), so I need a lot of hand-holding to reproduce anything in
> your setup, in particular how you are even getting extended characters
> to print (what locales and/or window settings you have to set).

1. You must run as a login shell, i.e. "bash -l"

2. You must have in /etc/profile, .profile or similar:

LANG=en_US.UTF-8


--
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-18  3:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 16:55 Eric Blake (cygwin)
2017-01-13  5:07 ` Steven Penny
2017-01-13 14:47   ` Eric Blake
2017-01-14  0:23     ` Steven Penny
2017-01-14 21:48       ` Eric Blake
2017-01-15  0:27         ` Steven Penny
2017-01-15 13:23           ` Vince Rice
2017-01-15 14:11             ` cyg Simple
2017-01-15 14:30               ` Steven Penny
2017-01-16 10:32                 ` Yaakov Selkowitz
2017-01-16 12:40                   ` Steven Penny
2017-01-15 22:33         ` Thomas Wolff
2017-01-16  0:45           ` Steven Penny
2017-01-16  0:54             ` Steven Penny
2017-01-17  2:47         ` Steven Penny
2017-01-17  3:32           ` Steven Penny
2017-01-18  0:36             ` Steven Penny
2017-01-18  2:08               ` Eric Blake
2017-01-18  3:55                 ` Steven Penny [this message]
2017-01-18  4:09                   ` Doug Henderson
2017-01-18  5:02                     ` Larry Hall (Cygwin)
2017-01-18  5:45                       ` Steven Penny
2017-01-19  5:23                         ` Steven Penny
2017-01-19 13:23                           ` Eliot Moss
2017-01-19 14:21                             ` Eric Blake
2017-01-19 18:13                               ` Corinna Vinschen
2017-01-19 23:54                                 ` Steven Penny
2017-01-20 13:04                                   ` Corinna Vinschen
2017-01-20 14:51                           ` Eric Blake
2017-01-20 15:00                             ` Eric Blake
2017-01-21  3:57                               ` Steven Penny
2017-01-18  1:46     ` Eric Blake

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=587ee723.e1039d0a.48332.ec2d@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).