Conversation
|
|
|
This also added benefit is that shortcut can be to chars long to choose a random letter if the first letter of a new aciton is already taken |
|
Through some discussion, it's better to get this correct instead to avoid the potential issues. Vite's dev server is commonly used to pair with other processes and it would not be great if there's subtle issues with those. I've made a poll (albeit only a small sample size) at https://twitter.com/bluwyoo/status/1704408350656782430 and https://elk.zone/m.webtoo.ls/@bluwy/111096467000284501. The rough average is that:
While it's still a significant portion of users who oppose this, the majority are still able to accept this. So we're going ahead with this change. |
|
Is there any way to get the original behaviour back? It is highly annoying. |
Description
Remove
setRawModefor shortcuts to prevent the following caveats:For the above reasons, it's best to not use
setRawModeand let the OS and Node.js handle the inputs as usual. The downside is that every shortcuts needs to be followed with anEnterpress to execute it (creates a new line to read the input).Close #11300
Close #14319
Close #11418
Additional context
What is the purpose of this pull request?