On Mon, Jul 02, 2012 at 12:08:05PM +0200, Hilko Bengen wrote: > reassign 679850 xterm > thank you > > >> Normally arrow keys generate the following codes: ^[[A, ^[[B, ^[[C, ^[[D (Up, > >> Down, Right, Left respectively). After running top(1) or any wine program in > >> XTerm these codes change to ^[OA, ^[OB, ^[OC, ^[OD. The only way I know to turn > >> them back is to reset the terminal. Bug is reproducible in any terminal > >> emulator and TTY if $TERM is set to "xterm" or "xterm-256color", so I'm not > >> sure if it's related to xterm itself. > > > > given that information, you're describing a bug in wine, > > and this should be reassigned accordingly. > > The submitter also mentioned top. I have just reproduced the behavior > with xterm 276-2 (but not with urxvt, running top (and not wine): shrug: reassign it to both. What you're describing is a well-known feature (normal versus application mode). A few entries don't set that (rxvt and linux), but the convention sets it. But assigning it to xterm (or ncurses) wastes my time, and only makes it harder for you to get my attention. The relevant place to start is with the applications that have a problem. > I don't even claim to know how terminal interaction works, but it is > clear that wine is not at fault here, so I am giving the bug to xterm. If you don't know what you're talking about, then why are you asserting your opinion? Start here: http://invisible-island.net/ncurses/ncurses.faq.html#cursor_appmode -- Thomas E. Dickey <dickey@invisible-island.net> http://invisible-island.net ftp://invisible-island.net
Attachment:
signature.asc
Description: Digital signature