Sorry for the top post...
I agree with Roy here, if we add the call we should spit out the
version of the curses lib. If someone tries to interpret the
contents of the return without consulting the man pages and derives
false information then that is their issue - really the call name
should be i
On 27/08/2019 21:14, Kamil Rytarowski wrote:
On 27.08.2019 19:29, Roy Marples wrote:
Using Blymns correct email :)
On 27/08/2019 18:28, Roy Marples wrote:
On 27/08/2019 17:24, Kamil Rytarowski wrote:
Last year, I wrote this patch to add curses_version() for curses(3).
http://netbsd.org/~kami
On 27.08.2019 19:29, Roy Marples wrote:
> Using Blymns correct email :)
>
> On 27/08/2019 18:28, Roy Marples wrote:
>> On 27/08/2019 17:24, Kamil Rytarowski wrote:
>>> Last year, I wrote this patch to add curses_version() for curses(3).
>>>
>>> http://netbsd.org/~kamil/patch-00073-curses-version.t
Using Blymns correct email :)
On 27/08/2019 18:28, Roy Marples wrote:
On 27/08/2019 17:24, Kamil Rytarowski wrote:
Last year, I wrote this patch to add curses_version() for curses(3).
http://netbsd.org/~kamil/patch-00073-curses-version.txt
The only purpose of this function is to get better co
On 27/08/2019 17:24, Kamil Rytarowski wrote:
Last year, I wrote this patch to add curses_version() for curses(3).
http://netbsd.org/~kamil/patch-00073-curses-version.txt
The only purpose of this function is to get better compat with ncurses
software.
I needed it originally in qemu. It's someti
Last year, I wrote this patch to add curses_version() for curses(3).
http://netbsd.org/~kamil/patch-00073-curses-version.txt
The only purpose of this function is to get better compat with ncurses
software.
I needed it originally in qemu. It's sometimes used in the wild.
Is it fine to merge it w
