Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Nov 2016 01:03:00 +0800
From:      Julian Elischer <julian@freebsd.org>
To:        Adrian Chadd <adrian.chadd@gmail.com>
Cc:        freebsd-current <freebsd-current@freebsd.org>
Subject:   Re: tput failing on 10 and 12 systems?
Message-ID:  <1b096f08-a63b-7254-58ba-9ee1ceb2ff5a@freebsd.org>
In-Reply-To: <CAJ-Vmo=sFViKYBWLCPmakq7oRB6jsyMzWVvFjTLTNzrg8gymbQ@mail.gmail.com>
References:  <834855a9-adcd-71b3-2422-e9eb97258486@freebsd.org> <CAJ-Vmo=sFViKYBWLCPmakq7oRB6jsyMzWVvFjTLTNzrg8gymbQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 22/11/2016 12:49 AM, Adrian Chadd wrote:
> Hiya,
>
> Just to follow through - part of tput is to decode command args, but
> it then just requests it from the ncurses tputs() call.
>
> So it could be tput, but it could also be the BSD ncurses work.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214709
>
>
> -adrian
>
>
> On 21 November 2016 at 07:54, Julian Elischer <julian@freebsd.org> wrote:
>> example on freefall     (FreeBSD 12.0-CURRENT #0 r306376)
>>
>> julian@freefall:tput setaf 4|od -c
>> 0000000  033   [   m
>> 0000003
>>
>> so nothing happens, and tput returns 1.
>>
>> but on a FreeBSD 8 system:
>>
>> [jelischer@alpha ~]$ tput setaf 4|od -c
>> 0000000  033   [   3   4   m
>> 0000005
>>
>> which make the text change color.
>>
>>
>> similarly all the related tput color commands I can think of fail on
>> 10,11,12
>>
>> but programs such as vim can use color just fine. So I suspect tput itself.
>>
>>
>> anyone have experience with this? seems easy to reproduce.
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1b096f08-a63b-7254-58ba-9ee1ceb2ff5a>