Simon Boudrias

Ah, yes. I'm open to adding this feature. We should be reusing the same interface as `description` in the Select prompt: https://github.com/SBoudrias/Inquirer.js/tree/main/packages/select#choice-object

@Sakthieswaran-tech go for it! 🎊

Would using [`description` on the choice object](https://github.com/SBoudrias/Inquirer.js/tree/main/packages/select#choice-object) work for this case? A side-by-side view I think adds a lot of complexity and UX questions.

I'm not sure that's a great match for the default prompts VS making a custom prompt you could release and maintain on npm. The use case and the UI appears...

The large piece of work is adding mode support with `` for search. If we go to that extent, then we should review the whole keybinding strategy rather than implement...

Yeah, currently it's a mix of the `useKeypress()` hook and a list of helper functions `isUpKey()`. If you can propose an implementation plan before moving into coding, it'd help making...

I like your idea with `useKeyNavigation` - it also allow to remove the long if/else conditions we have right now. I wouldn't however combine with `useKeypress` inside the prompts -...

How do you suggest handling combined keypresses like `3j` or `gg` with the `useKeypressHandler` interface?

Few comments: 1. Should `jumpWord` be abstracted away into `cursorRelative`? 2. `input`/`unhandledSequence` could also just be a `default` entry (kinda like a switch case.) Not sure if we need to...