Re: tin may ignore ncursesw (tin modifies terminal settings)

Thomas Dickey wrote:

> On Thu, 1 Apr 2010, clemens fischer wrote:
> 
>> I wrote, also in [1] about the same problem:
>>
>>> When I use "rtin", all the color settings affect only where "tin"
>>> writes text, everything else is left at the current default colors.
>>> I always thought this to be tin specific, but I am not so sure
>>> anymore, because after exiting "rtin", the same behaviour persists
>>> in "bash" as well!  I didn't notice until now, because tin runs
>>> always in its own tmux/screen managed window which closes after
>>> "rtin" exits.
> ...
>> I found that the binary links to /lib/libncursesw.so.5.7 (on
>> arch-linux) but apparently doesn't use all its entry points:
> 
> The first case is the termcap/terminfo interface, which isn't as
> clever as (n)curses in painting the proper text on the screen.  What
> you're describing sounds like a mismatch between the program/terminal
> for the "background color erase" feature.

That is what the tmux head dev thought, but BCE wasn't the problem.
I checked numerous times, tried all sorts of X11 resource settings for
both xterm and rxvt-unicode.  Then I found the "stub" curses/tcurses
implementations in tin's source and began to investigate that part of
the equation.  I would have never thought tin to use a mix of low-level
libcurses and terminfo routines, then tried to request libncursesw
explicitly in the ./configure step, which did the trick.

I think this should go into the FAQ.


clemens