[colug-432] Conflict btwn Screen and Putty

[George Larson]

Oh, man.  Apologies to OP.  I got caught up in the conversation about
tmux/screen.  Then, today, I ran into the problem on a FreeBSD box I was
setting up and realized I ignored the original question.

You can probably use those emacs-y alternatives like CTRL+A to go the
beginning of the line and CTRL + E to the end.

You can use 'cat' to figure out what key is being sent.  Just type 'cat',
hit enter and then if you press Home or Up Arrow or whatever, you'll see
the code that needs to be mapped, like in '/etc/inputrc' or '~/.inputrc' or
in ZSH I use 'bindkey'.

Hope that helps!  (:


On Wed, Mar 5, 2014 at 11:33 PM, George Larson <george.g.larson at gmail.com>wrote:

> Agreed about tmux.  I use tmux and gnu-screen literally every day on
> multiple machines.  It's tmux where I can get it and screen as a fallback.
>
> While we're at it, I don't use Windows much I recently I've started
> thinking I might like MobaXterm more then PuTTY.
> [  http://mobaxterm.mobatek.net  ]
>
>
> On Wed, Mar 5, 2014 at 10:14 PM, Jeff Stebelton <jeff.stebelton at gmail.com>wrote:
>
>> Heres a doc I put together today with the common commands from a web site
>> I found.
>>
>> I second the tmux suggestion. I'm not a hard core user but thats why I
>> second it. Really quite easy to get started but powerful enough to satisfy
>> the heavy duty user with all kinds of customization, scripting etc.
>> On Mar 5, 2014 9:29 PM, "Chris Clonch" <chris at theclonchs.com> wrote:
>>
>>>
>>> On 03/05/2014 09:23 AM, Joshua Kramer wrote:
>>>
>>> Hello Everyone,
>>>
>>> I have an odd conflict between screen (the terminal multiplexer) and
>>> Putty, and this is something I've never seen before.
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> 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?
>>>
>>>
>>> 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:
>>>
>>> find /usr/share/terminfo -type f
>>>
>>> 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.
>>>
>>> http://tmux.sourceforge.net/
>>>
>>> -Chris
>>>
>>>
>>> _______________________________________________
>>> colug-432 mailing list
>>> colug-432 at colug.net
>>> http://lists.colug.net/mailman/listinfo/colug-432
>>>
>>>
>> _______________________________________________
>> colug-432 mailing list
>> colug-432 at colug.net
>> http://lists.colug.net/mailman/listinfo/colug-432
>>
>>
>
>
> --
> -= c0d3 :: j0rg3 - all code, no cruft =- <http://j0rg3.com>
>



-- 
-= c0d3 :: j0rg3 - all code, no cruft =- <http://j0rg3.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.colug.net/pipermail/colug-432/attachments/20140306/ae687dc6/attachment.html