FS#63291 - [tmux] Erratic escape code handling in xterm

Attached to Project: Community Packages
Opened by Roland Venesz (steerio) - Saturday, 27 July 2019, 11:44 GMT
Last edited by Christian Hesse (eworm) - Wednesday, 21 August 2019, 19:26 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

The terminal behaves erratically in response to control codes used by tmux (and possibly other software). As tmux has not been updated recently and xterm had a new package yesterday (that I just installed), I attribute this behaviour change to xterm.

Additional info:
Package version: 348-1
Configuration:

XTerm*reverseVideo:off
XTerm*fullscreen:never
XTerm*faceName:Droid Sans Mono Slashed for Powerline
XTerm*faceSize:8
XTerm*foreground: rgb:c0/c0/c0
XTerm*background: rgb:00/00/00
...color definitions 0-15 follow...

Reproducing one manifestation of the bug:

* Start a tmux session
* Resize xterm window
* Split window horizontally
* Pane separator does not go all the way down

I'll update this bug report as I come upon additional, easily reproducible behaviour.
This task depends upon

Closed by  Christian Hesse (eworm)
Wednesday, 21 August 2019, 19:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  tmux 2.9_a-4
Comment by Roland Venesz (steerio) - Monday, 29 July 2019, 09:48 GMT
Splitting the window horizontally will exhibit all sorts of behaviour:

* Contents of one pane disappear when there is output in the other pane (even that of ls -l)
* Opening something in less or viewing tab completion options in the shell will push out the entire window, it essentially breaks out of the pane.

Most importantly, none of this happens in urxvt.

Additional information: my TERM environment variable (outside tmux of course) is xterm-256color.
Comment by Max Rees (sickbike) - Tuesday, 20 August 2019, 00:14 GMT
This is fixed in tmux upstream: https://github.com/tmux/tmux/commit/26f274011096b9eacfd2753d8f7afcb63e796ab9

Loading...