Open thillerson opened 9 years ago
If I had to guess without looking, this is most likely due to the dissonance between return
and enter
- two events get fired. Because different node versions change emitKeypressEvents, it's probably wise to add our own custom keypress parser there.
For some reason the 'select' event, hitting enter on an item in a List, fires twice.
On a Mac, I've tested in iTerm2 and Terminal.app using zshell. Compiled and run using coffee.
My List:
My Listener: @list.on('select', (item, index) => @itemSelected(index))