Re: Windows keyboard input

[Gavin Smith]

On 21 January 2017 at 07:55, Jason Hood <address@hidden> wrote:
> Attached is a patch to tweak Windows keyboard handling.  It adds
> a working 'pause_or_input' function, allowing echo area messages
> to be seen.  Windows 10 can now apparently seek console input, so
> just use GetConsoleMode to determine that.  Sets the 'term_??'
> definitions for KEY_HOME, KEY_END (and KEY_INSERT), allowing Home
> and End to be used in the echo area (rather than having to
> explicitly define 'M-<' and 'M->').

I have committed this patch with the following ChangeLog entry:

+2017-01-29  Jason Hood  <address@hidden>
+
+       * info/echo-area.c (pause_or_input) [__MINGW32__]: Add an
+       working implementation of this function, allowing echo area
+       messages to be seen.
+       * info/pcterm.c (gettextinfo):  Windows 10 can now apparently
+       seek console input, so just use GetConsoleMode to determine
+       that.
+       (pc_initialize_terminal) [_WIN32]: Sets the 'term_??'
+       definitions for KEY_HOME, KEY_END (and KEY_INSERT), allowing
+       Home and End to be used in the echo area (rather than having to
+       explicitly define 'M-<' and 'M->').
+       (w32_our_tty): Shorten function.

If this is wrong or misleading please tell me so I can fix it. (I do
not understand the change myself.) Also please feel free to report if
this patch works or not or if further changes are needed.