On Wed, Nov 08, 2017 at 01:04:31AM +, Christos Zoulas wrote:
> Even if we become bug compatible, we should keep a mode (via environment
> or program setting) that warns when we are asked to do something
> unspecified or different than the standard, or even behaves the way the
> standard mandate
On Wed, Nov 08, 2017 at 07:47:17 +1030, Brett Lymn wrote:
> On Mon, Nov 06, 2017 at 07:09:06PM +0300, Valery Ushakov wrote:
>
> This does leave us in the invidious position of our correctness
> being interpreted as bugs because we don't do what ncurses
> doesit is a constant, losing, battle.
On 11/8/2017 11:18 AM, Valery Ushakov wrote:
On Wed, Nov 08, 2017 at 07:47:17 +1030, Brett Lymn wrote:
On Mon, Nov 06, 2017 at 07:09:06PM +0300, Valery Ushakov wrote:
This does leave us in the invidious position of our correctness
being interpreted as bugs because we don't do what ncurses
does
On Wed, Nov 08, 2017 at 01:04:31AM +, Christos Zoulas wrote:
>
> Even if we become bug compatible, we should keep a mode (via environment
> or program setting) that warns when we are asked to do something
> unspecified or different than the standard, or even behaves the way the
> standard mand
In article <20171108210902.ga...@internode.on.net>,
Brett Lymn wrote:
>On Wed, Nov 08, 2017 at 01:04:31AM +, Christos Zoulas wrote:
>>
>> Even if we become bug compatible, we should keep a mode (via environment
>> or program setting) that warns when we are asked to do something
>> unspecifie
