Better to have the link to the direct bug issue.
Also because there you can have a sort of workaround:
- evaluate inline the readline command
- go to the terminal area of VSCODE
- type a space and enter a first time, and then the answer you want to give and enter again
The answer should now accounted for in the readline call.
I know it’s pretty ugly, but it can help while developing an old-style script-based application, if then the “user” is not supposed to use VSCODE itself…