From owner-freebsd-ports@freebsd.org  Tue May 16 18:55:32 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 5DAFED7017F
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Tue, 16 May 2017 18:55:32 +0000 (UTC) (envelope-from net@arrishq.net)
Received: from mail1.arrishq.net (eatmyshorts.phobos.ws [178.63.103.215])
 (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 E08A61981
 for <freebsd-ports@FreeBSD.org>; Tue, 16 May 2017 18:55:31 +0000 (UTC)
 (envelope-from net@arrishq.net)
Received: from mail.arrishq.net (mail.arrishq.net [127.0.0.1])
 (Authenticated sender: local)
 by mail1.arrishq.net (qmail) with ESMTPSA id A1266AAE ;
 Tue, 16 May 2017 20:49:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arrishq.net;
 s=default; t=1494960540;
 bh=b4BtD1vml7XW9iar3N5B3sC/WgosCJfqrTzfNu5Qw7Q=;
 h=Subject:To:Cc:References:From:Date:In-Reply-To;
 b=RKgCIGIU9k458Wld5OFTbk5S8tHn3DgT+9Y1najErxhyel6YKg2xKGUmTsYEQQiXa
 A1SqFt02UM4ckrNISdPRv7jcSnDKd8qTly6APab91qKdZpvi2R9UjNy3xAqJAPWLcF
 7lGUX9yrGCOkSnRK9rNvElN7yR8R31dh4EXKjKt8=
Subject: Re: sysutils/tmux - strange behaviour with new version 2.4
To: David Wolfskill <david@catwhisker.org>
Cc: freebsd-ports@FreeBSD.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>
From: Tommy Scheunemann <net@arrishq.net>
Message-ID: <c0dba2b0-6312-867d-a137-bcdc60c7f2a6@arrishq.net>
Date: Tue, 16 May 2017 20:48:56 +0200
MIME-Version: 1.0
In-Reply-To: <591AE823.8050809@quip.cz>
Content-Type: text/plain; charset=ISO-8859-1
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 18:55:32 -0000

Le 16.05.2017 à 13:53, Miroslav Lachman a écrit :
> David Wolfskill wrote on 2017/05/16 13:35:
>> Oddly enough, I saw the distinction you pointed out... even though I
>> read mail via mutt in a tmux window....  :-}
>
> Uhm... maybe it depends on source of the text? Or locale?

Hi,

I've been able to re-produce the issue, though setting:

set -g default-terminal "screen-256color"

in your tmux.conf seemed to help. Tested both under console and inside a
running urxvt.
Without that line:

env | grep TERM

gives me just "screen", having it set the above value. Dunno if that
might be related to /etc/termcap the screen line that exists (note -
dunno, unsure, just a guess).