Clarify READ_CHAR buffering

[ivar-rummelhoff]

As discussed, we should perhaps clarify whether READ_CHAR is supposed to receive each key press, or whether there should be some form of buffering. Ideally, a CLI interface would switch between the two: When the user must answer Y/N or select from a (short) menu, reading each key press is best; whereas if the input is – say – a complex search query, line buffering is more convenient, as it would allow the user to make corrections and adjustments using arrow keys, etc.

One solution might be to add one or more instructions for specifying the buffering, but maybe it is better to state that the user should be allowed to turn buffering on/off themselves? Alas, this could be rather confusing. For instance, if the user only remembers to turn on buffering after entering a few characters, then it would be too late to edit those characters. Moreover, we usually do not want the application to echo the input when using line buffering.