On 2/20/20, Lee wrote:
> I'll try backing out the registry change & see if it still happens.
It doesn't happen now.
I deleted HKEY_CURRENT_USER\Console\VirtualTerminalLevel
rebooted
deleted all the .o files under /source/tidy & rebuilt
The output of cmake looks normal
I updated cygwin this
On 2/20/20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 20:48:17 -0500
> Lee wrote:
>> On 2/20/20, Takashi Yano wrote:
>> > On Thu, 20 Feb 2020 16:28:26 -0500
>> > Lee wrote:
>> >> For whatever it's worth, the only problem I've noticed with 3.1.4 was
>> >> ansi control character handling and that
On 2/20/20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 18:34:59 -0700
> Brian Inglis wrote:
>> Windows programs which emit (or use?) console ANSI escape sequences run
>> from cmd
>> (which by default switches off Virtual Terminal ANSI Escape Sequence
>> handling
>> for programs run from it) and
On Thu, 20 Feb 2020 20:48:17 -0500
Lee wrote:
> On 2/20/20, Takashi Yano wrote:
> > On Thu, 20 Feb 2020 16:28:26 -0500
> > Lee wrote:
> >> For whatever it's worth, the only problem I've noticed with 3.1.4 was
> >> ansi control character handling and that was fixed by importing this
> >> bit into
Dear Cygwin,
My name is Russell.
Everyone wants to achieve better search rankings. Google's search engine uses a
variety of methods to determine, which pages are displayed first in the results.
If you've been working diligently on your web page optimization but it is not
getting the results you
On 2/20/20, Brian Inglis wrote:
> On 2020-02-20 18:27, Takashi Yano wrote:
>> On Thu, 20 Feb 2020 18:15:59 -0700
>> Brian Inglis wrote:
>>> On 2020-02-20 17:20, Takashi Yano wrote:
On Thu, 20 Feb 2020 16:28:26 -0500
Lee wrote:
> For whatever it's worth, the only problem I've noticed
On Thu, 20 Feb 2020 18:34:59 -0700
Brian Inglis wrote:
> Windows programs which emit (or use?) console ANSI escape sequences run from
> cmd
> (which by default switches off Virtual Terminal ANSI Escape Sequence handling
> for programs run from it) and which do not themselves set that console mode
On 2/20/20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 16:28:26 -0500
> Lee wrote:
>> For whatever it's worth, the only problem I've noticed with 3.1.4 was
>> ansi control character handling and that was fixed by importing this
>> bit into the registry:
>>
>> -
>> Windows Registry
On 2020-02-20 18:27, Takashi Yano wrote:
> On Thu, 20 Feb 2020 18:15:59 -0700
> Brian Inglis wrote:
>> On 2020-02-20 17:20, Takashi Yano wrote:
>>> On Thu, 20 Feb 2020 16:28:26 -0500
>>> Lee wrote:
For whatever it's worth, the only problem I've noticed with 3.1.4 was
ansi control
On Thu, 20 Feb 2020 18:15:59 -0700
Brian Inglis wrote:
> On 2020-02-20 17:20, Takashi Yano wrote:
> > On Thu, 20 Feb 2020 16:28:26 -0500
> > Lee wrote:
> >> For whatever it's worth, the only problem I've noticed with 3.1.4 was
> >> ansi control character handling and that was fixed by importing
On Fri, 21 Feb 2020 10:07:59 +0900
Takashi Yano wrote:
> Or just compile with:
> cl pipes.cpp /link /subsystem:console
Sorry, you need main() for this.
--
Takashi Yano
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
On 2020-02-20 17:20, Takashi Yano wrote:
> On Thu, 20 Feb 2020 16:28:26 -0500
> Lee wrote:
>> For whatever it's worth, the only problem I've noticed with 3.1.4 was
>> ansi control character handling and that was fixed by importing this
>> bit into the registry:
>>
>> -
>> Windows
On Fri, 21 Feb 2020 10:01:21 +0900
Takashi Yano wrote:
> On Thu, 20 Feb 2020 14:33:27 -0500
> Edward Lam wrote:
> > On Tue, Feb 18, 2020 at 2:43 PM Takashi Yano wrote:
> > > Could you please provide a simple test case?
> >
> > Here you go:
> >
> > // pipes.cpp
> > //
> > // Compile in a Visual
On Thu, 20 Feb 2020 14:33:27 -0500
Edward Lam wrote:
> On Tue, Feb 18, 2020 at 2:43 PM Takashi Yano wrote:
> > Could you please provide a simple test case?
>
> Here you go:
>
> // pipes.cpp
> //
> // Compile in a Visual Studio x64 Native Tools Command Prompt:
> // cl pipes.cpp /link
On Thu, 20 Feb 2020 16:28:26 -0500
Lee wrote:
> For whatever it's worth, the only problem I've noticed with 3.1.4 was
> ansi control character handling and that was fixed by importing this
> bit into the registry:
>
> -
> Windows Registry Editor Version 5.00
>
>
The following Perl distributions have been updated to their latest
version on CPAN, respectively:
x86/x86_64
--
perl-Cpanel-JSON-XS-4.19-1
perl-JSON-Parse-0.56-1
perl-Net-DNS-SEC-1.15-1
perl-Scalar-List-Utils-1.54-1
perl-Text-CSV_XS-1.41-1
noarch
--
perl-Alien-Build-2.08-1
The following Perl distributions have been updated to their latest
version on CPAN, respectively:
x86/x86_64
--
perl-Cpanel-JSON-XS-4.19-1
perl-JSON-Parse-0.56-1
perl-Net-DNS-SEC-1.15-1
perl-Scalar-List-Utils-1.54-1
perl-Text-CSV_XS-1.41-1
noarch
--
perl-Alien-Build-2.08-1
Thanks!
I was just sitting here thinking about the merits of verifying a new key
request like that by some kind of secure signature system, versus just posting
the request on a public mailing list, and having a human acknowledge to the
developer's previously known email address. I have to say,
On 20/02/2020 19:37, Andrew Schulman via cygwin-apps wrote:
Name: Andrew Schulman
Done.
On 2/20/20, Andrey Repin wrote:
> Greetings, KARL BOTTS!
>
>> I am worried. I need to instruct an IT department to install Cygwin. I
>> am
>> afraid that if I just tell them to run the installer, they will get an
>> unstable version. I am afraid other new users will be in the same boat.
>
>
Hi,
I would like to know if you're interested in acquiring "Salesforce Users
List" for your sales and marketing campaigns
We also have related technology users like: Netsuite, Infor, Oracle Siebel,
Microsoft Dynamics 365, Nimble, SAP, Sugar, Zoho, and many more.
Let me know if you are
Name: Andrew Schulman
Package: screen
BEGIN SSH2 PUBLIC KEY
E2VjZHNhLXNoYTItbmlzdHAzODQIbmlzdHAzODQAAABhBIh5WtQRqhzLyhiCds
BhExlJjXY+NeKxt7tp3l4ViEOwGAPmiMp9keikNzVrpBy2poorumkZDCJrCxx3855UxdnV
E51GAO7toxiCMM8BNHX3fnDj6rgydpjCNRStBQUqWQ==
END SSH2 PUBLIC KEY
Hi Takashi,
On Tue, Feb 18, 2020 at 2:43 PM Takashi Yano wrote:
> Could you please provide a simple test case?
Here you go:
// pipes.cpp
//
// Compile in a Visual Studio x64 Native Tools Command Prompt:
// cl pipes.cpp /link /subsystem:windows
//
// Run from inside a Cygwin shell, the
Greetings, KARL BOTTS!
> I am worried. I need to instruct an IT department to install Cygwin. I am
> afraid that if I just tell them to run the installer, they will get an
> unstable version. I am afraid other new users will be in the same boat.
Cygwin is a rolling release distribution.
JFYI:
Both 0x00 (NUL) and 0x7F (DEL) used to be the filler characters, and were
ignored by most (hardware) terminals from the very early days.
HTH,
Anton
> -Original Message-
> From: cygwin-patches-ow...@cygwin.com On
> Behalf Of Takashi Yano
> Sent: Thursday, February 20, 2020 6:52
On Feb 20 17:22, Thomas Wolff wrote:
> On 20.02.2020 17:04, Corinna Vinschen wrote:
> > On Feb 20 23:49, Takashi Yano wrote:
> > > On Thu, 20 Feb 2020 15:22:45 +0100
> > > Corinna Vinschen wrote:
> > > > On Feb 20 23:13, Takashi Yano wrote:
> > > > > On Thu, 20 Feb 2020 14:44:59 +0100
> > > > >
On 20.02.2020 17:04, Corinna Vinschen wrote:
On Feb 20 23:49, Takashi Yano wrote:
On Thu, 20 Feb 2020 15:22:45 +0100
Corinna Vinschen wrote:
On Feb 20 23:13, Takashi Yano wrote:
On Thu, 20 Feb 2020 14:44:59 +0100
Corinna Vinschen wrote:
On Feb 20 14:35, Corinna Vinschen wrote:
On Feb 20
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=c9f153580bfb4db4f9ef023b99360d7a746bd450
commit c9f153580bfb4db4f9ef023b99360d7a746bd450
Author: Corinna Vinschen
Date: Thu Feb 20 14:48:03 2020 +0100
Cygwin: console: ignore NUL byte on write in xterm emulation mode as well
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=4ec2e5e1c2d9bfdb742386a43a9d27aec4d74523
commit 4ec2e5e1c2d9bfdb742386a43a9d27aec4d74523
Author: Corinna Vinschen
Date: Thu Feb 20 14:57:26 2020 +0100
Cygwin: fhandler_console.cc: fix minor style issues
Signed-off-by:
On Feb 20 23:49, Takashi Yano wrote:
> On Thu, 20 Feb 2020 15:22:45 +0100
> Corinna Vinschen wrote:
> > On Feb 20 23:13, Takashi Yano wrote:
> > > On Thu, 20 Feb 2020 14:44:59 +0100
> > > Corinna Vinschen wrote:
> > > > On Feb 20 14:35, Corinna Vinschen wrote:
> > > > > On Feb 20 20:51, Takashi
On 19/02/2020 23:41, Alexey Sokolov wrote:
19.02.2020 17:44, Jon Turney пишет:
On 18/02/2020 19:53, Marco Atzeri wrote:
Am 16.02.2020 um 16:30 schrieb Jon Turney:
On 16/02/2020 08:08, Marco Atzeri wrote:
Am 16.02.2020 um 07:55 schrieb ASSI:
Marco Atzeri writes:
Perhaps I should just
On Thu, 20 Feb 2020 15:22:45 +0100
Corinna Vinschen wrote:
> On Feb 20 23:13, Takashi Yano wrote:
> > On Thu, 20 Feb 2020 14:44:59 +0100
> > Corinna Vinschen wrote:
> > > On Feb 20 14:35, Corinna Vinschen wrote:
> > > > On Feb 20 20:51, Takashi Yano wrote:
> > > > > - In xterm compatible mode,
Some further investigations.
1. I missed the comment "default is set". So setting CYGWIN=glob is
irrelevant. I may still want to set CYGWIN=glob:ignorecase, but that's
a separate matter.
2. With forward slashes, globbing works as expected:
E:\Utils\Cygwin64\bin\echo E:/Work/Scratch/m*.py
On Feb 20 23:13, Takashi Yano wrote:
> On Thu, 20 Feb 2020 14:44:59 +0100
> Corinna Vinschen wrote:
> > On Feb 20 14:35, Corinna Vinschen wrote:
> > > On Feb 20 20:51, Takashi Yano wrote:
> > > > - In xterm compatible mode, 0x00 on write() behaves incompatible
> > > > with real xterm. In xterm,
On Thu, 20 Feb 2020 14:44:59 +0100
Corinna Vinschen wrote:
> On Feb 20 14:35, Corinna Vinschen wrote:
> > On Feb 20 20:51, Takashi Yano wrote:
> > > - In xterm compatible mode, 0x00 on write() behaves incompatible
> > > with real xterm. In xterm, 0x00 completely ignored. Therefore,
> > > 0x00
I am worried. I need to instruct an IT department to install Cygwin. I am
afraid that if I just tell them to run the installer, they will get an
unstable version. I am afraid other new users will be in the same boat.
I am fine for myself: I am on Cygwin 3.07, it is a tank, and I can stay
On Feb 20 14:35, Corinna Vinschen wrote:
> On Feb 20 20:51, Takashi Yano wrote:
> > - In xterm compatible mode, 0x00 on write() behaves incompatible
> > with real xterm. In xterm, 0x00 completely ignored. Therefore,
> > 0x00 is ignored by console with this patch.
> > ---
> >
On Feb 20 20:51, Takashi Yano wrote:
> - In xterm compatible mode, 0x00 on write() behaves incompatible
> with real xterm. In xterm, 0x00 completely ignored. Therefore,
> 0x00 is ignored by console with this patch.
> ---
> winsup/cygwin/fhandler_console.cc | 10 ++
> 1 file changed,
> I also found this does not occur if
> vbell off
> is added to .screenrc
oh! thanks a lot, it a really helpful suggestion
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:
> In cygwin 3.1.0 or later, Alt-space sends ESC+SPACE (0x1b 0x20)
> to client as linux console.
> The new feature is disabled if legacy console mode is enabled,
> so it behaves as you expected with some sacrifice.
ok, i understood, but it sad
use CTRL+SHIFT+V
instead ALT+SPACE+3 times UP+RIGHT+2
- In xterm compatible mode, 0x00 on write() behaves incompatible
with real xterm. In xterm, 0x00 completely ignored. Therefore,
0x00 is ignored by console with this patch.
---
winsup/cygwin/fhandler_console.cc | 10 ++
1 file changed, 10 insertions(+)
diff --git
Hello,
I discovered that the mingw cross compilers for i686 and x86-64 have a
problem with support of pkg-config. From what I have seen, the mingw
included into CYGWIN is not using the usual pkg-config, but it uses
pkgconf instead, which is a good thing at first sight, since it does
not depend to
On Thu, 20 Feb 2020 14:51:21 +0500
Eugene Klimov wrote:
> > > press ALT+SPACE doesn't work
> > That's because the cygwin console handler interprets Alt+Space itself
> > and sends ESC Space. Same behaviour in mintty if you disable the "Menu
> > and Full screen" option.
> how to turn off interprets
On Thu, 20 Feb 2020 09:50:44 +0500
Eugene Klimov wrote:
> > > inside windows 10 (build 1909)
> > > just open WIN+R cmd.exe
> > This start cmd.exe.
> > > type
> > > `ssh root@my_redhat_entrise_linux_7.2`
> > This uses windows OpenSSH to connect linux.
> no, i install cygwin ssh package
> and i have
> > press ALT+SPACE doesn't work
> That's because the cygwin console handler interprets Alt+Space itself
> and sends ESC Space. Same behaviour in mintty if you disable the "Menu
> and Full screen" option.
how to turn off interprets ALT+SPACE by cygwin console and pass this
hotkey to window
On 20.02.2020 05:00, Eugene Klimov wrote:
additional have you tried to set "disable_pcon" ?
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
yes i tried
WIN+R
cmd.exe
```
C:\cygwin64>SET CYGWIN=disable_pcon
C:\cygwin64>echo %CYGWIN%
disable_pcon
```
press ALT+SPACE - worked, window menu
On 19.02.2020 21:21, Brian Inglis wrote:
On 2020-02-19 13:02, Kevin Schnitzius via cygwin wrote:
On Tuesday, February 18, 2020, 05:54:23 PM EST, Thomas Wolff wrote:
With 3.1.2-1:
mintty -o "CA+F12:break" => ctrl-alt-F12 causes a break
and kills notepad
mintty -o "c:break"
47 matches
Mail list logo
