Interactive programs are broken

[raszuk]

When executing any program or script which requires user confirmation to continue for example rm -i or unzip or even plane read bash function more then once ... the script-server does not pass pressed letter without enter which messes up second request as {ENTER} from the buffer is then considered as second input.

Then it works on the third and fails on the fourth etc ...

[bugy]

Hi @raszuk thanks for reporting.
It's not completely a bug: it's a mix between UX and expected behaviour in 80% cases.
There are 20% cases, when only a single character is expected or even some action buttons (e.g. arrows). I think there should be a separate input mode for it, which should be changeable via UI, and a default mode can depend on a script config

[raszuk]

@bugy True that in some cases I could see that entering word(s) with enter can be also useful. I think this 20% vs 80% depends on which side you seat :) For me this is 80% vs 20% :)