* 0: As usual.
* 1: Windows 10 version 1809
* The bug causes unstable handling of ambiguous width character.
- * 2: Windows 10 version 1903
+ * 2: Windows 10 version 1903 & 1909
* Use the wrong result because each result is different.
* 3: Windows 10 insider preview (current latest logic)
*/
++cmdbase;
// Check the command does not begin with "start "
- if (cmdbase == NULL
- || STRNICMP(cmdbase, "start", 5) != 0 || !VIM_ISWHITE(cmdbase[5]))
+ if (cmdbase == NULL || STRNICMP(cmdbase, "start", 5) != 0
+ || !VIM_ISWHITE(cmdbase[5]))
{
// Use a terminal window to run the command in.
x = mch_call_shell_terminal(cmd, options);
*/
#define CONPTY_1903_BUILD MAKE_VER(10, 0, 18362)
+/*
+ * version 1909 (November 2019 update).
+ */
+#define CONPTY_1909_BUILD MAKE_VER(10, 0, 18363)
+
/*
* Confirm until this version. Also the logic changes.
* insider preview.
if (ver <= CONPTY_INSIDER_BUILD)
conpty_type = 3;
+ if (ver <= CONPTY_1909_BUILD)
+ conpty_type = 2;
if (ver <= CONPTY_1903_BUILD)
conpty_type = 2;
if (ver < CONPTY_FIRST_SUPPORT_BUILD)