-   Slackware (
-   -   Character set problem in tmux on Slack (

astanton 06-16-2012 11:01 PM

Character set problem in tmux on Slack
1 Attachment(s)
I get the following annoyances when I do the following:

Running KDE on Slackware, I open terminal, ssh into a remote machine, start tmux.

This doesn't happen running tmux sessions on my own Slackware machine and ssh into other machines, and It doesn't seem to happen on all of the machines that I ssh into and run tmux.

Is this some character set issue that I need to change on either my local Slackware workstation or the remote hosts that I have this problem with?

If so, then how/what/where do I change on my local machine? I would ask what I should do on the remote hosts but if those aren't Slackware machines it might be an off-topic question, but I'll take all comers.

This is what I have on my Slackware box at this time:


# set | grep LANG

The remote machine in the image is a CentOS 6 machine, and what it should be displaying is a single, thin green horizontal line, and in the bottom portion a single, thin green vertical line.

I've noticed that I don't have this problem with screen, but I prefer tmux.

bosth 06-17-2012 01:42 AM

Try a UTF-8 locale on your local machine:

My guess is that tmux is drawing lines with utf8-encoded characters that require two bytes.

astanton 06-17-2012 05:02 AM

Another reason why Slackware "Just works".
I switched my character sets around via .profile, .bashrc, and a simple export on the command line.

No matter what I did, it didn't break tmux in Slackware locally. I ssh'd into the CentOS box from a debian box - same thing. on deb it's fine whatever character set I used.

I figured the same thing you were suggesting up until that point and then I ssh'd into the CentOS box from my Slackware workstation. Upon checking, the character set was en_US.UTF-8 so I...


export LANG=en_US
from a bash prompt and guess what? tmux isn't broken anymore!

I wonder if that has anything to do with why tmux isn't in the standard RH/CentOS repos, and one has to get it instead from repoforge.

Now I'm wondering what I may have broken on the CentOS box elsewhere LOL!

Anyone have any ideas?

All times are GMT -5. The time now is 09:09 AM.