On 2019-01-30 11:40, Andrey Repin wrote:
>> I've always used "^\s+keyword\s" as a way to search for some keyword
>> starting a section.
> Welcome to the club.
>> On linux it still works, but on cygin it doesn't like '\s' as symbol for
>> white space.
>> Any idea why there might be a difference?
>>
On Wed, Jan 30, 2019 at 4:23 PM Corinna Vinschen
wrote:
> > > > Poking around further, I find that replacing the signal generation
> > > > code in the test program for all cases with :
> > > >
> > > > pthread_kill(pthread_self(),sigid)
> > > >
> > > > generates compliant signal delivery behavior
Hi folks,
I uploaded a new Cygwin test release 3.0.0-0.3
This release comes with a couple of new features and some interesting
bug fixes.
It also changes the output of uname(2) for newly built applications.
Applications built so far (that includes uname(1) from coreutils)
will still print the o
On Jan 30 16:48, Corinna Vinschen wrote:
> On Jan 30 11:44, Corinna Vinschen wrote:
> > On Jan 29 18:21, Dan Bonachea wrote:
> > > > A minimal test program is copied below and also available here:
> > > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> > >
> > > > It's worth noting POSIX
On Wed, Jan 30, 2019 at 11:09 AM Eric Blake wrote:
> Not so much compilation options of man and less, but rather the code
> used in Cygwin itself for handling regex.
The configuration of less supports many different regex libraries. I
downloaded the source and ran "./configure --with-regex=pcre"
On Jan 30 20:01, Corinna Vinschen wrote:
> On Jan 30 19:53, Corinna Vinschen wrote:
> > On Jan 30 11:47, Brian Inglis wrote:
> > > On 2019-01-30 10:31, Corinna Vinschen wrote:
> > > > On Jan 30 09:11, Brian Inglis wrote:
> > > >> On 2019-01-30 07:03, Corinna Vinschen wrote:
> > > >>> I uploaded a n
On 1/30/19 1:09 PM, Eric Blake wrote:
> \s is a non-standard regex extension - glibc provides it, Cygwin has not
> (at least, historically). POSIX provides [[:space:]] as a portable
> alternative (although not all libc have implemented all of POSIX yet),
> but is annoyingly long to type.
>
> Sim
On Jan 30 13:09, Eric Blake wrote:
> On 1/30/19 12:40 PM, Andrey Repin wrote:
>
> >
> > I've been puzzled by this since… forever, it seems.
> > This is something in less, but all the `man less` says is "regular
> > expression
> > library provided by your system".
>
> \s is a non-standard regex
On 1/30/19 12:40 PM, Andrey Repin wrote:
>
> I've been puzzled by this since… forever, it seems.
> This is something in less, but all the `man less` says is "regular expression
> library provided by your system".
\s is a non-standard regex extension - glibc provides it, Cygwin has not
(at least,
Greetings, Brian Inglis!
> Re: "(*) It would really be nice not having to ask for these infos every
> time."
> may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/UBR to
> uname -s sysname to show the patch levels of installed builds, as there
> appears
> to be substantial diffe
On Jan 30 19:53, Corinna Vinschen wrote:
> On Jan 30 11:47, Brian Inglis wrote:
> > On 2019-01-30 10:31, Corinna Vinschen wrote:
> > > On Jan 30 09:11, Brian Inglis wrote:
> > >> On 2019-01-30 07:03, Corinna Vinschen wrote:
> > >>> I uploaded a new Cygwin test release 3.0.0-0.2
> > >>> It also chan
On Jan 30 11:47, Brian Inglis wrote:
> On 2019-01-30 10:31, Corinna Vinschen wrote:
> > On Jan 30 09:11, Brian Inglis wrote:
> >> On 2019-01-30 07:03, Corinna Vinschen wrote:
> >>> I uploaded a new Cygwin test release 3.0.0-0.2
> >>> It also changes the output of uname(2) for newly built applicatio
Greetings, L A Walsh!
> I've always used "^\s+keyword\s" as a way to search for some
> keyword starting a section.
Welcome to the club.
> On linux it still works, but on cygin it doesn't like '\s' as
> symbol for white space.
> Any idea why there might be a difference?
> I note an option that
On 2019-01-30 10:31, Corinna Vinschen wrote:
> On Jan 30 09:11, Brian Inglis wrote:
>> On 2019-01-30 07:03, Corinna Vinschen wrote:
>>> I uploaded a new Cygwin test release 3.0.0-0.2
>>> It also changes the output of uname(2) for newly built applications.
>>> Applications built so far (that include
On Wed, Jan 30, 2019 at 11:31 AM Corinna Vinschen
wrote:
>
> On Jan 30 09:11, Brian Inglis wrote:
> >
> > Re: "(*) It would really be nice not having to ask for these infos every
> > time."
> > may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/UBR to
> > uname -s sysname to sho
On Jan 30 09:11, Brian Inglis wrote:
> On 2019-01-30 07:03, Corinna Vinschen wrote:
> > I uploaded a new Cygwin test release 3.0.0-0.2
> > It also changes the output of uname(2) for newly built applications.
> > Applications built so far (that includes uname(1) from coreutils)
> > will still print
On 2019-01-30 07:03, Corinna Vinschen wrote:
> I uploaded a new Cygwin test release 3.0.0-0.2
> It also changes the output of uname(2) for newly built applications.
> Applications built so far (that includes uname(1) from coreutils)
> will still print the old uname output. The new format allows fo
On Jan 30 11:44, Corinna Vinschen wrote:
> On Jan 29 18:21, Dan Bonachea wrote:
> > > A minimal test program is copied below and also available here:
> > > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
> >
> > > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > > specific
On Jan 30 14:18, Corinna Vinschen wrote:
> On Jan 30 12:43, Christian Franke wrote:
> > Corinna Vinschen wrote:
> > > I uploaded a new Cygwin test release 3.0.0-0.1
> > >
> > > ...
> > > What's new:
> > > ---
> > >
> > > ...
> > >
> > > - Support for case sensitive directories. mkdir(2)
Hi folks,
I uploaded a new Cygwin test release 3.0.0-0.2
This release comes with a couple of new features and some interesting
bug fixes.
It also changes the output of uname(2) for newly built applications.
Applications built so far (that includes uname(1) from coreutils)
will still print the o
On Jan 29 16:45, Steven Penny wrote:
> On Tue, 29 Jan 2019 20:59:59, Corinna Vinschen wrote:
> > - New file ioctls's FS_IOC_GETFLAGS and FS_IOC_SETFLAGS. The actual
> > inode flags are Cygwin-specific. This allows to set or reset
> > DOS attributes, file sparseness, FS level encryption and co
On Jan 30 12:43, Christian Franke wrote:
> Corinna Vinschen wrote:
> > I uploaded a new Cygwin test release 3.0.0-0.1
> >
> > ...
> > What's new:
> > ---
> >
> > ...
> >
> > - Support for case sensitive directories. mkdir(2) automatically
> >creates directories within the Cygwin ins
Corinna Vinschen wrote:
I uploaded a new Cygwin test release 3.0.0-0.1
...
What's new:
---
...
- Support for case sensitive directories. mkdir(2) automatically
creates directories within the Cygwin installation dir as case
sensitive now.
This feature requires Windows 10 1803
On Jan 29 23:50, Denis Excoffier wrote:
> Hello,
>
> I tried the (numerous) recent snapshots with W10 (1709) with no
> problem (except for the isolated 20190115 snapshot and also that « cp
> cygwin0.dll /usr/bin/cygwin1.dll » now fails but this is another
> story). The recent snapshots with W7 fai
On Jan 29 18:21, Dan Bonachea wrote:
> > A minimal test program is copied below and also available here:
> > https://upc-bugs.lbl.gov/bugzilla/attachment.cgi?id=589
>
> > It's worth noting POSIX 1003.1-2016 sec XRAT.B.2.4.1 (p.3577)
> > specifically requires that any given signal should be deliver
On 2019-01-30 00:15, LRN wrote:
> On 28.01.2019 17:02, LRN wrote:
>> This[0] and this[1]. One header checks for atomic C/CXX extensions *and* for
>> the presence of a C++ compiler, while the other only checks for extensions.
>> The result is that the _Atomic() macro is *not* defined in cdefs.h when
26 matches
Mail list logo
