Selecta could/should allow use of up/down arrows about selecta HOT 7 CLOSED

#76
#71
#15

from selecta.

@rschmitt woops. Sorry for the noise...
So after reading a bit... Is this supposed to work now or not?

from selecta.

No. I believe it was supported for a brief period, but that support was dropped due to inconsistent behavior on different platforms (sometimes it worked, sometimes it didn't). Ctrl-N and Ctrl-P have always worked, however. There is an open issue on a Selecta clone (felipesere/icepick#27) that has proposed the tab key as an alternative to the down arrow.

from selecta.

@rschmitt Then this issue is valid :) The arrow key processing requires that you way a small delay to see if other chars come in. I haven't implemented this recently, but I can dig up some old python code if needed. If OSX is doing something dumb, then we should ignore that, or just switch based on $TERM or similar...

from selecta.

Are you also aware of the cursor mode issues discussed in #76 (comment)?

from selecta.

@rschmitt I did see this yes. Sounds like there's a bug in here or rather in some lib somewhere... I don't have a patch to offer (sorry) but +1 to whoever fixes this :)

from selecta.

The bug is in the design of the VT100 protocol. ;) ESC means multiple things and the only way to distinguish between them is by waiting and guessing. Selecta does VT100 for output, but not for input, because I don't want to (1) maintain code for input escape codes, or (2) depend on a giant library from the 80s. Fortunately, ^P and ^N work everywhere in Unix (even in Vim!), so switching to them is a good idea anyway.

from selecta.