440 reputation
312
bio website
location Tokyo, Japan
age 28
visits member for 3 years, 2 months
seen Aug 29 at 1:53

Computational scientist lost in Japan


Mar
28
awarded  Notable Question
Aug
20
comment change colours when running screen
Have you tried TERM=xterm-256color tmux to start tmux?
Aug
16
awarded  Popular Question
Aug
8
awarded  Popular Question
Apr
3
comment tmux exits with [exited] on mac os x
I recently found (for the first time) that if 1) .tmux.conf exists but has syntax errors or 2) .tmux.conf is a symbolic link that links to nothing, tmux will not open. It might be good to try at first with the default configuration file so first mv $HOME/.tmux.conf $HOME/.tmux.conf.backup and see if tmux starts. @ChrisJohnsen is right, your solution simply means that there is a bug afoot.
Apr
3
revised Setup mutt to read through a threaded message and then return to the email index
Tried to make the title easier to understand :\
Apr
2
awarded  Tumbleweed
Mar
26
asked Setup mutt to read through a threaded message and then return to the email index
Feb
18
comment How can you use the domain of the client connected over ssh in the shell?
thanks for that, but it seems these files are binary log files and are difficult to parse. Using cat spills a lot of junk to the screen and parsing it would be a pain, although they interestingly seem to have logs for each day of the past week. I'll investigate if there is a good way to use it.
Feb
18
revised How can you use the domain of the client connected over ssh in the shell?
added 131 characters in body
Feb
18
comment How can you use the domain of the client connected over ssh in the shell?
Thanks for that, it will help in some instances such as OpenSUSE, which has this log (though it seems to spit out a lot of garbage, too), but I am currently interested in OSX which is a variant of BSD. Unfortunately, this is not a log file in OSX.
Feb
18
asked How can you use the domain of the client connected over ssh in the shell?
Jan
26
answered bind tmux prefix to OS X cmd key (or any other binding)
Nov
22
comment tmux: sharing current window title (#T) from within nested tmux sessions
@elliottcable I just want to add one more point. If you use this and are worried, I suggest doing it ONLY before attaching to a session that does not display the same pane AND you should reset the variable after your session detaches export TERM=$TEMP_TERM
Nov
22
comment tmux: sharing current window title (#T) from within nested tmux sessions
@elliottcable yes, you are right, it does say that. My solution to this problem is more or less a hack. This can mess up your session and may even freeze up slow computers, but I am not certain this is something I am worried about. For example, if you reset TERM to anything other than screen* then you end up running tmux attach-session -t $(tmux display -p "#S") you will setup an infinite loop of tmux nested sessions (chaos!). I am not sure of any other, more extreme examples of possible problems, but you should certainly avoid infinite loops :)
Sep
7
awarded  Commentator
Sep
7
comment UTF-8 Not Working in PuTTY when using SSH Remote command
@Navarr, I agree that it is strange behavior. I suspect that PUTTY may be forcing a different TERM or LANG variable when connecting using the "remote command". There may be an option for this, but I have limited experience with PUTTY (perhaps remote-command: "source $HOME/.bashrc" would help the mystery?). In principle, the only reason to use putty's "remote-command" is to run a program and have the shell quit after it finishes (i.e. the shell exits after you detach). With my work-around, you should be able to just close the window and have no problems because tmux should automatically detach.
Sep
6
answered UTF-8 Not Working in PuTTY when using SSH Remote command
Sep
5
comment UTF-8 Not Working in PuTTY when using SSH Remote command
Sorry, also, it might be helpful to know what value of LANG you are using echo $LANG
Sep
5
comment UTF-8 Not Working in PuTTY when using SSH Remote command
No problem, when you connect to the remote machine without "remote command", type echo $TERM (this tells you the value of TERM), I expect "xterm" or something similar. Attach the session and check the output of the same command (it won't be the same). Also, when you connect with "remote connection" being "tmux attach" give the output of the same command, I expect "screen" or something similar. Next, just to make sure, you setup putty to display UTF-8? Also, have you added set term_charset in the irrsi config files?