On Wed, 22 Mar 2017 16:15:21, cyg Simple wrote:
Which goes to further state that this isn't Cygwin but a library package
used by bash. Cygwin is the POSIX glue to the packages; I know that
everyone wants to think of the entire set as Cygwin but that isn't
really true. Cygwin is managing to pres
On 3/20/2017 6:49 PM, Steven Penny wrote:
> On Mon, 20 Mar 2017 15:06:26, cyg Simple wrote:
>> This really isn't a Cygwin issue as I see it. What occurs if you run
>> your mingw32.exe in a CMD command window? This may be a mintty issue
>> but certainly not because of Cygwin itself. But even the
On Mon, 20 Mar 2017 15:06:26, cyg Simple wrote:
This really isn't a Cygwin issue as I see it. What occurs if you run
your mingw32.exe in a CMD command window? This may be a mintty issue
but certainly not because of Cygwin itself. But even the mintty case is
dependent on the results you see in
On 3/19/2017 12:23 AM, Steven Penny wrote:
> On Fri, 3 Feb 2017 09:39:47, Corinna Vinschen wrote:
>> 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.
>
> Sorry for delayed response. I knew I had a reason f
On Fri, 3 Feb 2017 09:39:47, Corinna Vinschen wrote:
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.
Sorry for delayed response. I knew I had a reason for this, but honestly forgot
what it was. Here is th
On Fri, 03 Feb 2017 04:48:49, Steven Penny wrote:
> On Fri, 03 Feb 2017 10:30:23, Houder wrote:
> > Apologies for the confusion ... the unicode symbol I was pasting in was
> > the latin small letter o with diaeresis ...
> > For some reason something went wrong when I composed my e-mail.
>
> I had
On Fri, 03 Feb 2017 10:30:23, Houder wrote:
> Apologies for the confusion ... the unicode symbol I was pasting in was
> the latin small letter o with diaeresis ...
> For some reason something went wrong when I composed my e-mail.
I had the same problem. You need to add
Content-Type: text; cha
On Fri, 03 Feb 2017 10:09:51, Houder wrote:
> On Fri, 3 Feb 2017 09:39:47, Corinna Vinschen wrote:
>
> > Cygwin 2.7.0:
> >
> > Works in tcsh and dash, even with chcp 65001. Does not work with
> > bash for some reason in cp 65001.
>
> Using the Windows Console:
>
> 64 LANG = en_US.UTF-8, LC_ALL
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
On Fri, 3 Feb 2017 09:39:47, Corinna Vinschen wrote:
> Cygwin 2.7.0:
>
> Works in tcsh and dash, even with chcp 65001. Does not work with
> bash for some reason in cp 65001.
Using the Windows Console:
64 LANG = en_US.UTF-8, LC_ALL =
=> LANG = en_US.UTF-8
64-@@ cygcheck -sv | awk '$1 ~ /^(libre
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
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
On Thu, 02 Feb 2017 16:08:37, Steven Penny wrote:
> Which will allow Alt 148 to work as expected:
> ö
> However once you change the code page:
> $ chcp.com 65001
> Active code page: 65001
Ok, I found that if I install cygwin-2.7.0 and libreadline7-7.0.1-2 then this
works as exepcted
On Thu, 2 Feb 2017 14:30:48, Corinna Vinschen wrote:
> Under cygwin 2.7.0 this works fine for me in tcsh, bash 4.4.11-2, bash
> 4.4.12-3 and od, including Alt +f6. That is, as long as I'm in the
> Windows console. Mintty only supports Alt +f6 or Alt 246 when in
> Unicode mode.
With a clean envir
On Feb 2 04:50, Steven Penny wrote:
> On Wed, 01 Feb 2017 21:21:41, Steven Penny wrote:
> > Resending these example with proper charset. Here is example that worked pre
> > 2.7.0:
> > Ω%
> > Here is example that did not work pre 2.7.0:
> > %Ω
>
> It looks like I spoke too soon. For some r
On Feb 1 21:21, Steven Penny wrote:
> On Wed, 01 Feb 2017 19:18:49, Steven Penny wrote:
> > Ω%
> > %Ω
>
> Resending these example with proper charset. Here is example that worked pre
> 2.7.0:
>
> Ω%
>
> Here is example that did not work pre 2.7.0:
>
> %Ω
>
> Again, these are bot
On Wed, 01 Feb 2017 21:21:41, Steven Penny wrote:
> Resending these example with proper charset. Here is example that worked pre
> 2.7.0:
> Ω%
> Here is example that did not work pre 2.7.0:
> %Ω
It looks like I spoke too soon. For some reason LATIN SMALL LETTER O WITH
DIAERESIS' (U+00F6) i
On Wed, 01 Feb 2017 19:18:49, Steven Penny wrote:
> Ω%
> %Ω
Resending these example with proper charset. Here is example that worked pre
2.7.0:
Ω%
Here is example that did not work pre 2.7.0:
%Ω
Again, these are both working now.
--
Problem reports: http://cygwin.com/prob
On Tue, 31 Jan 2017 16:42:41, Corinna Vinschen wrote:
> - Fix handling of Alt-Numpad sequences in console handler.
> Addresses: https://cygwin.com/ml/cygwin/2017-01/msg00135.html
> - Fix erasing UTF-8 multibyte characters in cooked mode.
> Addresses: https://cygwin.com/ml/cygwin/2017-01/msg002
Hi folks,
I uploaded a new Cygwin test release 2.7.0-0.1
Apart from the changes mentioned below, there's another patch in the
loop speeding up network access in scenarios with slower round trip
time (most everything on the internet), but I'm still waiting for
input from the patch provider.
20 matches
Mail list logo
