On 2013-02-03, 07:51, Andre Goree wrote:
I'm having an issue with tmux on certain ssh connections. When I
connect to my freebsd server's tmux session that has multiple panes in
one window, everything looks fine. However, when I connect to my linux
box, I get this weird character [1] instead
On 02/03/13 08:06, Schaich Alonso wrote:
On 2013-02-03, 07:51, Andre Goree wrote:
I'm having an issue with tmux on certain ssh connections. When I
connect to my freebsd server's tmux session that has multiple panes in
one window, everything looks fine. However, when I connect to my linux
On Sun, 03 Feb 2013 11:54:16 -0500, Andre Goree wrote:
On a related note, I guess I can set LANG=en_US.UTF-8 in my .bashrc and
have that as my default, no?
As far as I remember, login.conf is the file to set this, but
you can basically set environmental variables wherever you want.
For example,
On Sun, 03 Feb 2013 11:54:16 -0500
Andre Goree an...@drenet.info wrote:
Thanks! That was it...I opened a new konsole window, set the encoding
to UTF-8 (which my arch linux box is using) and the lines show up fine.
On a related note, I guess I can set LANG=en_US.UTF-8 in my .bashrc and
have
I'm having an issue with tmux on certain ssh connections. When I
connect to my freebsd server's tmux session that has multiple panes in
one window, everything looks fine. However, when I connect to my linux
box, I get this weird character [1] instead of a line as I would expect.
Any ideas on
On 2/2/2013 11:05 AM, Andre Goree wrote:
Thanks, I'm actually using bash as a shell, probably should've mentioned
that. Anywho:
[agoree@desktop ~]$ grep TERM .*
.bash_history:echo $TERM
.profile:# Setting TERM is normally done through /etc/ttys. Do only
override
.profile:# TERM=cons25;
On 02/02/13 12:30, Joshua Isom wrote:
On 2/2/2013 11:05 AM, Andre Goree wrote:
Thanks, I'm actually using bash as a shell, probably should've mentioned
that. Anywho:
[agoree@desktop ~]$ grep TERM .*
.bash_history:echo $TERM
.profile:# Setting TERM is normally done through /etc/ttys. Do