From owner-freebsd-ports@freebsd.org  Tue May 16 19:51:52 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8DD4D708DB
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue, 16 May 2017 19:51:52 +0000 (UTC)
 (envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AADCECE
 for <freebsd-ports@freebsd.org>; Tue, 16 May 2017 19:51:52 +0000 (UTC)
 (envelope-from 000.fbsd@quip.cz)
Received: from elsa.codelab.cz (localhost [127.0.0.1])
 by elsa.codelab.cz (Postfix) with ESMTP id 4AF7928433;
 Tue, 16 May 2017 21:51:49 +0200 (CEST)
Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz
 [86.49.16.209])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by elsa.codelab.cz (Postfix) with ESMTPSA id 3AEEB28411;
 Tue, 16 May 2017 21:51:48 +0200 (CEST)
Subject: Re: sysutils/tmux - strange behaviour with new version 2.4
To: Freddie Cash <fjwcash@gmail.com>
Cc: Tommy Scheunemann <net@arrishq.net>,
 freebsd-ports <freebsd-ports@freebsd.org>,
 David Wolfskill <david@catwhisker.org>
References: <5919E2CE.5010109@quip.cz>
 <40137405-2db0-759f-46d5-67519703d48f@FreeBSD.org> <591AE179.6030107@quip.cz>
 <20170516113522.GU1146@albert.catwhisker.org> <591AE823.8050809@quip.cz>
 <c0dba2b0-6312-867d-a137-bcdc60c7f2a6@arrishq.net> <591B507D.2040403@quip.cz>
 <CAOjFWZ7nF7j3_o85_1aX2cA_3G6cvobNSjpFCENg_YM7eQcZcw@mail.gmail.com>
From: Miroslav Lachman <000.fbsd@quip.cz>
Message-ID: <591B5854.305@quip.cz>
Date: Tue, 16 May 2017 21:51:48 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101
 Firefox/42.0 SeaMonkey/2.39
MIME-Version: 1.0
In-Reply-To: <CAOjFWZ7nF7j3_o85_1aX2cA_3G6cvobNSjpFCENg_YM7eQcZcw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 May 2017 19:51:52 -0000

Freddie Cash wrote on 2017/05/16 21:27:
> On Tue, May 16, 2017 at 12:18 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote:

[snip]

>> # env | grep TERM
>> TERM=screen-256color
>>
>> And missing lines are different on each run.
>>
>
> ​Just curious, but what happens if you set TERM=tmux instead of
> TERM=screen?  Newer versions of tmux accept that as an option, and the
> termcap/terminfo should be cleaner/more up-to-date than the screen setting.​
>
> ​From:​
>
> https://www.freebsd.org/cgi/man.cgi?query=tmux&sektion=1&apropos=0&manpath=FreeBSD+11.0-RELEASE+and+Ports
>
> ​"​default-terminal terminal
>      Set the default terminal for new windows created in this session
>      - the default value of the TERM environment variable.  For tmux
>      to work correctly, this must be set to `screen', `tmux' or a
>      derivative of them."

I tried this in ~/.tmux.conf:

set -g default-terminal "tmux"

But when I run tmux command I got this error:

tcsh: Cannot open /etc/termcap.
tcsh: using dumb terminal settings.

I think there is no tmux entry in /etc/termcap on FreeBSD 10.3

And tmux output with dumb terminal is still misbehaving.

Miroslav Lachman