On Wed, Apr 06, 2022 at 01:28:56PM -, Christos Zoulas wrote:
>
> 1. Is there a way to have a "compatibility mode"? Or is that too complicated
>or unwanted?
I could make a compile time option to switch back to the old behaviour.
I just tried it and curses seems to work, I don't think the s
No major bump seems to be required, and if not required, should
not happen.
Even a minor number bump sounds from your descriptions to be
not required, but those are harmless, and at least easily allow
the installed version to be discovered (for bug reports etc),
so that one I would recommend.
Som
Brett Lymn writes:
> So, the point of all this blather is even though there have been no
> interface changes as a result of my work there is the potential for a
> significant visual change. Should I mark this with a libcurses major
> bump? I don't think it necessary but I am putting it out ther
In article ,
Brett Lymn wrote:
>
>Folks,
>
>This started out innocuously enough, I picked up a PR about fileobj from
>pkgsrc not working properly. This was partially an upstream problem but
>also an issue with our curses chgat() function. After a bit of digging
>I found two things. Firstly,
Hi Brett,
> So, the point of all this blather is even though there have been no
> interface changes as a result of my work there is the potential for a
> significant visual change. Should I mark this with a libcurses major
> bump? I don't think it necessary but I am putting it out there for
> dis
Folks,
This started out innocuously enough, I picked up a PR about fileobj from
pkgsrc not working properly. This was partially an upstream problem but
also an issue with our curses chgat() function. After a bit of digging
I found two things. Firstly, every other colour capable implementat
