The tab key produces the event EvKey (KASCII 'i') [MCtrl] instead of the expected EvKey (KASCII '\t') []

[coconnor]

1. cd vty/test
2. runghc Test.hs
3. Press tab

the event printed is EvKey? (KASCII 'i') [MCtrl]

[coconnor]

The raw bytes read from STDIN for 4 tabs followed by ESC are:

'\t'
'\t'
'\t'
'\t'
'\ESC'

Which is what is expected. Looks like it's post STDIN read where the error occurs.

[coconnor]

Using a MacBook? Pro, Terminal, Mac OS X 10.5.3 the control-i sequence produces a sequence identical to the tab key. In the classify table here is a mapping from the tab key to KASCII tab:

("\t",(KASCII '\t',[]))

but there is also a mapping from the tab key to control-i:

("\t",(KASCII 'i',[MCtrl]))

[coconnor]

They are equivalent input for many terminals. I'm not sure why the control-I event is now selected over the tab event. In this case "\t" should trigger only a KASCII '\t' event. Never a CONTROL-I event. However, I could see the desire for:

1. Supporting CONTROL-I events for those terminals that do differentiate between the two.
2. Optionally remapping CONTROL-I to TAB implicitly.

[anonymous]

Reproduced in VTY 3.0.1. So not a regression caused by new input thread handling. Also does not explain exactly *why* there was a regression in yi!