win32: reset errno in read_key()

The WIN32 implementation of read_key() didn't reset errno to zero,
unlike the upstream version.  This could result in invalid non-zero
errno values after calls to lineedit_read_key().

For example, after an attempt to run a non-existent command in the
shell errno is set to ENOENT.  If the shell had vi line edit mode
enabled any command that reads an additional character (e.g. 'c' or
'd') would see the non-zero errno and report EOF.

(GitHub issue #283)

0 files changed, 0 insertions, 0 deletions