Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Border not displaying correctly? #224

Closed
sbacic opened this issue Dec 1, 2015 · 20 comments
Closed

Border not displaying correctly? #224

sbacic opened this issue Dec 1, 2015 · 20 comments

Comments

@sbacic
Copy link

sbacic commented Dec 1, 2015

Here are some screenshots:

https://imgur.com/a/Ljmz2

Basically, every time the rightmost panel is selected, the border does not go all the way. There are also some (possibly unrelated) issues with mouse text select with the select overflowing into other panes.

I'm running tmux inside a docker container (ubuntu:trusty). The same issue does not exist on the host system (Elementary OS Freya).

@nicm
Copy link
Member

nicm commented Dec 1, 2015

tmux version? terminal? TERM inside and outside tmux? Are you using UTF-8?

@sbacic
Copy link
Author

sbacic commented Dec 1, 2015

Tmux version is 2.0 in container, 1.8 on host, but I'm reasonably sure that I had that problem on 1.8 as well (probably why I upgraded to 2.0, thinking it would go away).
TERM returns the same on both host and container - xterm outside and screen inside tmux.
For UTF-8, I tried printing the EURO sign, works fine on both host and container.

Not sure what you mean by terminal...

I've also noticed one other thing that might help; if I open something like midnight commander in the right pane, it shows the borders fine, but if I open in the left and then switch focus between them I get something like this: https://imgur.com/tvSd4h8. Tmux doesn't freeze.

@nicm
Copy link
Member

nicm commented Dec 1, 2015

What terminal are you running tmux inside?

@sbacic
Copy link
Author

sbacic commented Dec 1, 2015

You mean the host OS terminal application? That would be pantheon-terminal.

@nicm
Copy link
Member

nicm commented Dec 1, 2015

Does it still happen in xterm?

@sbacic
Copy link
Author

sbacic commented Dec 1, 2015

Installed xterm on host and started the docker instance in it. The issue persists.

@nicm
Copy link
Member

nicm commented Dec 1, 2015

Hmm. Please run "tmux -vvvv -f /dev/null -Ltest new" then reproduce the problem and send me the tmux-*.log files.

@sbacic
Copy link
Author

sbacic commented Dec 2, 2015

Here are the log files. All I did was open tmux, created another pane and switched between them.
http://s000.tinyupload.com/index.php?file_id=02153881842721797464

@nicm
Copy link
Member

nicm commented Dec 2, 2015

If you put just this in terminal-overrides, does it fix the problem:

set -ag terminal-overrides ',*:cud1=\E[1B'

@nicm
Copy link
Member

nicm commented Dec 2, 2015

I edited the previous comment, make sure you include the comma:

set -ag terminal-overrides ',*:cud1=\E[1B'

@sbacic
Copy link
Author

sbacic commented Dec 2, 2015

I've just tested the fix you provided and it appears to be working properly now. The border is displaying properly and there are no more graphical anomalies. Can you tell me what happened?

@nicm
Copy link
Member

nicm commented Dec 2, 2015

Something has a bug and is treating LF (\n) like CRLF (\r\n). In non-canonical mode, LF should just move the cursor one line down, it should not also move it to the start of the line. Since it is the same in xterm I suspect it is not the terminal itself, what else is getting the data between tmux and xterm?

@sbacic
Copy link
Author

sbacic commented Dec 2, 2015

First off, I ran this from pantheon-terminal, not xterm. And the only thing between them is the docker container (without any processes running, other than bash).

@nicm
Copy link
Member

nicm commented Dec 2, 2015

But you tried it in xterm earlier right and the bug was still there?

@sbacic
Copy link
Author

sbacic commented Dec 2, 2015

Yes, of course. Both the bug and solution work in xterm and pantheon-terminal. As far as I'm concerned, this problem is solved you can close this issue.

In case somebody with this same problem Googles the issue (broken border/graphic artifacts in tmux under docker), here's the solution: just add

set -ag terminal-overrides ',*:cud1=\E[1B'

to your .tmux.conf file (mine is in ~/.tmux.conf).

@nicm
Copy link
Member

nicm commented Dec 2, 2015

I expect this is a bug in docker or in your Linux install, you may see other problems too since \n is not behaving as expected.

@nicm nicm closed this as completed Dec 2, 2015
@tarvos21
Copy link

tarvos21 commented Jan 3, 2017

screenshot from 2017-01-03 16-09-11
 
Hi, anyone still there? I have encountered the same problem with the pane border line.
 
When I split the screen into left and right panes, then split the right pane into up and down panes, the horizontal border line does not work properly, it expands to the left pane which has not been split. As shown in the picture above, the horizontal line goes to the left pane, and overrides the contents(line 27) in it.
 
My tmux is 2.1, on Ubuntu 16.04, not container. I use default Ternimal on Ubuntu. I use UTF-8.
 
I have tried the solution provided above, but it does not work. The pane border still acts weirdly.

@sbacic
Copy link
Author

sbacic commented Jan 11, 2017

Hi there, sorry for the late reply. I've moved on from the setup described in the issue so I'm afraid I can't help you much. Sorry :(

@hitochan777
Copy link

@tarvos21 I had a similar issue as yours. I fixed the problem by changing "ambiguous-width chars" setting from "full width" to "half width" in gnome terminal. ("Edit" -> "Profile Preferences" -> "Compatibility" -> "Ambiguous-width chars").
I don't know if you have this option because I use Japanese remix version.

@lock
Copy link

lock bot commented Feb 15, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

4 participants