Issue 1 in wy60: With TERM=xterm, wy60 behaves badly.

[codesite...@google.com]

Comment #6 on issue 1 by zod...@gmail.com: With TERM=xterm, wy60 behaves
badly.
http://code.google.com/p/wy60/issues/detail?id=1

I like having individual issues in the issue tracker, if it is something I
need to
act on. So, yes, if you need changes made, want to suggest patches, have
questions
and similar things then please do open a new issue for each one of them.

And yes, I am definitely interested in getting a more complete set of escape
sequences, if that helps make things easier for users.

I just created a new Google Group and set it up to automatically receive
all changes
made to this project (including new issues, code changes, new
comments, ...). Feel
free to post to the group, if you think that is more appropriate than using
any of
the other features on the project site.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #7 on issue 1 by dic...@his.com: With TERM=xterm, wy60 behaves
badly.
http://code.google.com/p/wy60/issues/detail?id=1

xterm and wy60 (wyse60) aren't really compatible.
Run "infocmp xterm wy60" to see some of the differences.

[codesite...@google.com]

Comment #8 on issue 1 by zod...@gmail.com: With TERM=xterm, wy60 behaves
badly.
http://code.google.com/p/wy60/issues/detail?id=1

Of course they are different. That's the whole point of the "wy60" project.
It
dynamically translates between "wy60" and "xterm" escape sequences.