Date: Tue, 16 May 2017 20:48:56 +0200 From: Tommy Scheunemann <net@arrishq.net> To: David Wolfskill <david@catwhisker.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: sysutils/tmux - strange behaviour with new version 2.4 Message-ID: <c0dba2b0-6312-867d-a137-bcdc60c7f2a6@arrishq.net> In-Reply-To: <591AE823.8050809@quip.cz> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c0dba2b0-6312-867d-a137-bcdc60c7f2a6>