> On Dec 15, 2017, at 7:33 AM, Steven Penny wrote:
>
> On Thu, 14 Dec 2017 14:57:14, Ken Brown wrote:
>> And, as I said, it happens when setup is *preparing* to download files and
>> finds a corrupt copy already present in the local cache. In that context,
>> setup has no idea where the file came
On Thu, 14 Dec 2017, Corinna Vinschen wrote:
Hi Mark,
Thanks for sigtimedwait! Two questions:
On Dec 13 22:54, Mark Geisert wrote:
diff --git a/winsup/cygwin/signal.cc b/winsup/cygwin/signal.cc
index 69c5e2aad..0599d8a3e 100644
--- a/winsup/cygwin/signal.cc
+++ b/winsup/cygwin/signal.cc
Abstract out common code from sigwait/sigwaitinfo/sigtimedwait to implement the
latter.
---
winsup/cygwin/common.din | 1 +
winsup/cygwin/include/cygwin/version.h | 3 ++-
winsup/cygwin/signal.cc| 36 --
winsup/cygwin/thread.cc
On Thu, 14 Dec 2017 14:57:14, Ken Brown wrote:
And, as I said, it happens when setup is *preparing* to download files and
finds a corrupt copy already present in the local cache. In that context,
setup has no idea where the file came from.
the point is, *it doesnt matter*. it is not and
On 2017-12-12 12:42, Thomas Taylor wrote:
> I believe that Cygwin displays certain UTF-8 characters incorrectly. To see
> the
> problem, first save the attached "utf-8_test.sed" text file to your desktop.
> Then run "mintty," and set its options by right clicking in its title bar,
> selecting
On 2017-12-14 12:32, Gianpaolo Pedrazza wrote:
> On mar, 2017-12-12 at 09:07 -0700, Brian Inglis wrote:
> I had a look, but I couldn't do too much and decided to go through
> another way. Apparently there is a patch that can be applied to the
> libnet source files before compiling the library
Jon Turney writes:
> A new setup release candidate is available at:
>
> https://cygwin.com/setup/setup-2.883.x86.exe(32 bit version)
> https://cygwin.com/setup/setup-2.883.x86_64.exe (64 bit version)
I couldn't give it much testing, but I've built this version for both
arches locally and
On 12/14/2017 2:46 PM, Andrey Repin wrote:
Greetings, Ken Brown!
This is a followup to the discussion started here:
https://cygwin.com/ml/cygwin/2017-12/msg00088.html
When setup is preparing to download files and it finds a corrupt copy in
the local cache, it issues a fatal error
Greetings, Ken Brown!
> This is a followup to the discussion started here:
>https://cygwin.com/ml/cygwin/2017-12/msg00088.html
> When setup is preparing to download files and it finds a corrupt copy in
> the local cache, it issues a fatal error message telling the user to
> remove the
On mar, 2017-12-12 at 09:07 -0700, Brian Inglis wrote:
> > I need to install libnet and I found on various sites [2][3] that
> > the
> > only one way to install the prerequisite libpcap is to extract the
> > Developer Pack [4] into cygwin. I did it, I run all the tests and
> > the
> > pcap library
Greetings, Thomas Taylor!
> I believe that Cygwin displays certain UTF-8 characters incorrectly. To
> see the problem, first save the attached "utf-8_test.sed" text file to
> your desktop.
First, your "NBSP" is actually
http://www.fileformat.info/info/unicode/char/23b5/index.htm
> Then run
On 2017-12-11 16:36, Thomas Taylor wrote:
> Thank you for your advice on setting my locale to en_US.UTF-8. Unfortunately,
> Cygwin still seems to have trouble displaying some three-byte UTF-8 encoded
> characters correctly. For example, see the following snippet from a "sed"
> file. This file
Am 14.12.2017 um 17:21 schrieb cyg Simple:
On 12/14/2017 3:55 AM, Thomas Wolff wrote:> Mintty interfaces to Windows
using the Unicode/UTF-16 API, so there is
no dependency on the Windows system locale.
I assume the original poster's problem is a font issue, unless a test
case would demonstrate
On 12/14/2017 3:55 AM, Thomas Wolff wrote:> Mintty interfaces to Windows
using the Unicode/UTF-16 API, so there is
> no dependency on the Windows system locale.
> I assume the original poster's problem is a font issue, unless a test
> case would demonstrate anything else.
> Thomas
>
I seem to
On 12/13/2017 11:40 PM, Brian Inglis wrote:
> On 2017-12-13 00:50, Thomas Wolff wrote:
>> Am 13.12.2017 um 06:21 schrieb Brian Inglis:
>>> On 2017-12-04 18:23, Thomas Taylor wrote:
>>> Your Windows Regional settings and your mintty/Options/Text/Language and
>>> Character Set should be set to
Hi Mark,
Thanks for sigtimedwait! Two questions:
On Dec 13 22:54, Mark Geisert wrote:
> diff --git a/winsup/cygwin/signal.cc b/winsup/cygwin/signal.cc
> index 69c5e2aad..0599d8a3e 100644
> --- a/winsup/cygwin/signal.cc
> +++ b/winsup/cygwin/signal.cc
> [...]
> + }
> +
Am 14.12.2017 um 05:40 schrieb Brian Inglis:
On 2017-12-13 00:50, Thomas Wolff wrote:
Am 13.12.2017 um 06:21 schrieb Brian Inglis:
On 2017-12-04 18:23, Thomas Taylor wrote:
Your Windows Regional settings and your mintty/Options/Text/Language and
Character Set should be set to match.
The
17 matches
Mail list logo
