Anonymous - 2010-09-06

iTerm is no longer being developed, but this bug is not reproducable in iTerm2 at http://code.google.com/p/iterm2