Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread Christos Zoulas
On Oct 22, 11:04am, k...@munnari.oz.au (Robert Elz) wrote: -- Subject: Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be | Yes, you mentioned that one yesterday, that is certainly a possibility, | though it does mean that apps that include (most likely | indirectly because of incl

Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread Robert Elz
Date:Sun, 22 Oct 2017 12:44:54 -0400 From:chris...@zoulas.com (Christos Zoulas) Message-ID: <20171022164454.08b6617f...@rebar.astron.com> | Yes, and they should (have that defined) since this header is really part | of the implementation and should not be included

Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread David Holland
On Mon, Oct 23, 2017 at 12:33:05AM +0700, Robert Elz wrote: > I am beginning to agree. I have ruled out simply moving struct winsize > from ttycom.h to termios.h - that breaks in-tree code, Which? (i.e. which part of the logic I offered yesterday has a wrong premise?) -- David A. Holland dhol

Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread Kamil Rytarowski
On 22.10.2017 07:19, Robert Elz wrote: > Not really (aside from quoting glibc as being an example of how things > should be done is usually just funny) - apps can define as many of those > symbols as they need, the lines from featuretest.h that I quoted are > just picking the default. Just to be c

Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread Robert Elz
Date:Sun, 22 Oct 2017 19:47:27 + From:David Holland Message-ID: <20171022194727.ga27...@netbsd.org> | Which? (i.e. which part of the logic I offered yesterday has a wrong | premise?) That it is OK to break old sources doing things the way that it has been (an

Re: FYI: POSIX update - SIGWINCH and 'struct winsize' (etc) to be added

2017-10-22 Thread Robert Elz
Earlier I asked... | Could we perhaps use Christos' method, with the addition of modifying | so that instead of just | | #include | | it instead has ... | | #if defined(_NETBSD_SOURCE) | #include | #else | #define _NETBSD_SOURCE 1 | #include | #undef _NETBSD_SOURCE