Wrong cursor keycodes with modifiers in app cursor mode

[GoogleCodeExporter]

The keycodes sent by the cursor keys do not agree with xterm when a
modifier key is pressed and the terminal is in application cursor keys mode.

For example, unmodified arrow-up sends '\eOA' when in app cursor mode, and 
'\e[A' otherwise. Similarly, currently shifted arrow-up sends '\eO1;2A'
when in app cursor mode, and '\e[1;2A' otherwise.

In xterm, however, modified cursor keys actually always send codes starting
with '\e[1;', no matter the app cursor mode parameter.

Original issue reported on code.google.com by andy.koppe on 12 Jan 2009 at 9:49

[GoogleCodeExporter]

Fixed in r109 on 0.3 branch.

Original comment by andy.koppe on 12 Jan 2009 at 10:05

• Changed state: Fixed

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by andy.koppe on 14 Jan 2009 at 7:40

• Changed state: Verified