Issue 2927 in iterm2: Seeing text mangled and arrow escape codes randomly

6 views
Skip to first unread message

ite...@googlecode.com

unread,
Mar 11, 2014, 5:30:58 PM3/11/14
to iterm2...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 2927 by vcut...@gmail.com: Seeing text mangled and arrow escape
codes randomly
http://code.google.com/p/iterm2/issues/detail?id=2927

** READ THIS **
ATTACH YOUR ~/Library/Preferences/com.googlecode.iterm2.plist FILE TO THIS
ISSUE!
Almost all issues are configuration-specific. Issues missing this file will
be closed.

Many issues require a debug log. Save time by attaching one now!
https://code.google.com/p/iterm2/wiki/DebugLogging

Performance issues usually require sampling.
https://code.google.com/p/iterm2/wiki/HowToSample



What steps will reproduce the problem?
1. Download keyremap4macbook install it
2. Set delay until repeat to be 300 ms
3. Set key repeat to be sub 80 seconds
4. When you quickly typing in the shell or using arrows keys to complete
history you will start to see text get mangled or escape codes (for arrows)
getting entered into the terminal for text.

What is the expected output?
For iterm 2 to function the same as terminal.app

What do you see instead?
I see arrow escape codes appear randomly and text that gets mangled
randomly when typing quickly

What version of iTerm2 are you using?
Build 1.0.0.20140112

What OS version are you using?
10.8.5

Please provide any additional information below.
I have a feeling this might have to do with iterm 2 expecting the delay
until repeat and key repeat to be at 500ms or greater? Earlier version of
iterm2 were working fine when I had keyremap4macbook installed. (earlier
meaning awhile ago)





Attachments:
com.googlecode.iterm2.plist 45.4 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

ite...@googlecode.com

unread,
Mar 11, 2014, 5:31:58 PM3/11/14
to iterm2...@googlegroups.com

Comment #1 on issue 2927 by vcut...@gmail.com: Seeing text mangled and
2. Set delay until repeat to be 300 ms
or less

ite...@googlecode.com

unread,
Mar 13, 2014, 2:51:43 AM3/13/14
to iterm2...@googlegroups.com

Comment #2 on issue 2927 by gnach...@gmail.com: Seeing text mangled and
Can you make a debug log?
https://code.google.com/p/iterm2/wiki/DebugLogging

ite...@googlecode.com

unread,
Mar 13, 2014, 4:20:07 PM3/13/14
to iterm2...@googlegroups.com

Comment #3 on issue 2927 by vcut...@gmail.com: Seeing text mangled and
here ya go

Attachments:
debuglog.txt.gz 2.1 MB

ite...@googlecode.com

unread,
Mar 14, 2014, 1:09:15 AM3/14/14
to iterm2...@googlegroups.com

Comment #4 on issue 2927 by gnach...@gmail.com: Seeing text mangled and
Looks like your shell was unhappy for some reason. We sent esc [ A, which
is the right thing to do when you press up. Your shell responded with a
bell and [A, suggesting it didn't parse the escape code properly. I don't
think iTerm is doing anything wrong here.

ite...@googlecode.com

unread,
Mar 14, 2014, 1:15:50 AM3/14/14
to iterm2...@googlegroups.com

Comment #5 on issue 2927 by vcut...@gmail.com: Seeing text mangled and
Ok I scoured my bashrc but maybe I missed something.. I'll start setting up
a bare bones one and test a bit thank you

ite...@googlecode.com

unread,
Mar 14, 2014, 2:58:43 AM3/14/14
to iterm2...@googlegroups.com

Comment #6 on issue 2927 by gnach...@gmail.com: Seeing text mangled and
It's not something you can fix with bashrc, it's actually a bug in bash. I
reported it but they didn't think it was worth fixing. The only solution is
to paste slower.
Reply all
Reply to author
Forward
0 new messages