<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 03/05/2014 09:23 AM, Joshua Kramer
wrote:<br>
</div>
<blockquote
cite="mid:CAMPA5gfoQ9yCB1-BG_qhSS2CB9WpABOFAxPm96ZbeSBqj8Y8iQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello Everyone,<br>
<br>
I have an odd conflict between screen (the terminal multiplexer)
and Putty, and this is something I've never seen before.<br>
<br>
The environment is RedHat 5.8. It's worth noting that when I
was using CentOS 5.x on a daily basis, I used Putty and screen
all the time without encountering this problem.<br>
<br>
Normally, when you login via putty with bash as your shell, you
can hit the up-arrow for the last command. This sends the ascii
code for ESC, then [A, and it goes across to bash (or whatever
other program) just fine. When you try this via screen, it
looks like the terminal manager in screen takes "the ascii code
for ESC, then [A" and turns it into the actual character string
^[[A, which is Caret + [ + [ + A.<br>
<br>
I was always able to sort out these kinds of issues on my own
systems by setting TERM=xterm and the Putty terminal emulation
to xterm. That doesn't work in this case. Where should I start
looking for possible solutions to this problem?<br>
</div>
</blockquote>
<br>
My guess is an issue with term settings between Putty, screen and
your shell. It has been ages since I've ran screen so my memory is
a little fuzzy, but I believe screen would set your TERM to
"screen". You might check to see if you have term definition for
screen:<br>
<br>
<code>find /usr/share/terminfo -type f</code><br>
<br>
Not sure if it is an option, but you might switch to tmux from
screen. So many improvements over screen it is hard to start.<br>
<br>
<a class="moz-txt-link-freetext" href="http://tmux.sourceforge.net/">http://tmux.sourceforge.net/</a><br>
<br>
-Chris<br>
<br>
</body>
</html>