In case anyone runs into this problem on older versions of FreeBSD (or
anything else), I was able to resolve it by copying over the relevant
xterm-256color definitions from FreeBSD 10, and tmux now starts up
correctly without having to force it with -2.
On Fri, Sep 5, 2014 at 1:50 PM, Patrick <gibblert...@gmail.com> wrote:
> Yeah, I have TERM=xterm-256color. Prior to upgrading from 1.8 to 1.9a, it
> worked fine. Before loading tmux, my test script works fine:
>
> http://cl.ly/image/0C2605003n3W
>
> Once tmux is loaded, the script fails to output more than 16... unless I
> start it up with -2. The host system is FreeBSD 8.4. I'll continue to see
> if I can figure it out...
>
>
>
> On Wed, Sep 3, 2014 at 10:29 PM, Nicholas Marriott <
> nicholas.marri...@gmail.com> wrote:
>
>> Make sure your TERM outside tmux is 256 colours, or use
>> terminal-overrides to make tmux think it is.
>>
>> Eg in xterm use xterm-256color
>>
>>
>>
>> -------- Original message --------
>> From: Patrick <gibblert...@gmail.com>
>> Date: 04/09/2014 00:00 (GMT+00:00)
>> To: tmux-users@lists.sourceforge.net
>> Subject: tmux.conf equivalent for -2?
>>
>>
>> Since upgrading to tmux 1.9a, tmux is no longer able to detect that my
>> terminal has 256 colors; I have to invoke it with -2. Is there an
>> equivalent option in tmux.conf to force this mode so that I don't need to
>> use the -2 option?
>>
>
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
