Thanks to @vgoklani for suggesting that I try iTerm2 and tmux. iTerm2 is a replacement for the OSX Terminal program and tmux is an alternative to the ‘screen’ command.
This is how I set them up on my Macbook Pro and on the remote Debian Squeeze computer I’m using:
On Debian Squeeze:
The version installed by using
sudo apt-get install tmux
doesn’t work with iTerm2 on mac – it needs the special iTerm2 version (although it seems like it will be merged into the main tmux development in the future).
So instead do this:
wget https://github.com/downloads/libevent/libevent/libevent-2.0.19-stable.tar.gz tar -zxvf libevent-2.0.19-stable.tar.gz cd libevent-2.0.19-stable/ ./configure make sudo make install wget http://iterm2.googlecode.com/files/tmux-for-iTerm2-20120203.tar.gz tar -zxvf tmux-for-iTerm2-20120203.tar.gz cd tmux-for-iTerm2-20120203/ sh autogen.sh ./configure make sudo make install
To get it to work, I also had to do this:
sudo ln -s /usr/local/lib/libevent-2.0.so.5 /usr/lib64/libevent-2.0.so.5
On Mac OS X
Download and install https://github.com/downloads/libevent/libevent/libevent-2.0.19-stable.tar.gz
(can use same command line steps as on debian)
I think the same tmux-for-iTerm2 steps as on debian would probably work but I downloaded and installed the one that said it was for OS X 10.7.2 instead (tmux-for-iTerm2-20120203-precompiled.tar.gz). I still used configure and make to build and install it.
Finally install iTerm2 itself:
tmux seems very useful for interactive sessions, especially with the integration into iTerm2. But I’m not sure what I’d gain by changing
startupRemotePython.sh (see yesterdays post) to use tmux on the remote server? I also couldn’t work out how to do it. Any suggestions?