Permalink
Browse files

patch 8.0.0993: sometimes an xterm sends an extra CTRL-X

Problem:    Sometimes an xterm sends an extra CTRL-X after the response for
            the background color.  Related to t_RS.
Solution:   Check for the CTRL-X after the terminating 0x7.
  • Loading branch information...
brammool committed Aug 24, 2017
1 parent 33d66bd commit f6d9f96b2d67327bbadd7210acc7c6028439bbcd
Showing with 6 additions and 0 deletions.
  1. +4 −0 src/term.c
  2. +2 −0 src/version.c
View
@@ -4626,6 +4626,10 @@ check_termcode(
key_name[0] = (int)KS_EXTRA;
key_name[1] = (int)KE_IGNORE;
slen = i + 1 + (tp[i] == ESC);
if (tp[i] == 0x07 && i + 1 < len && tp[i + 1] == 0x18)
/* Sometimes the 0x07 is followed by 0x18, unclear

This comment has been minimized.

Show comment
Hide comment
@dezza

dezza Aug 25, 2017

If I add a LOG_TR("Catch CTRL+X") so slen is always incremented it fixes my issue with mintty. If this is not the intended behaviour then mintty is broken and should be handled specially. A mintty can identify itself via "\033[>c" I have tried to get this string with TGETSTR but failed.

@dezza

dezza Aug 25, 2017

If I add a LOG_TR("Catch CTRL+X") so slen is always incremented it fixes my issue with mintty. If this is not the intended behaviour then mintty is broken and should be handled specially. A mintty can identify itself via "\033[>c" I have tried to get this string with TGETSTR but failed.

* when this happens. */
++slen;
break;
}
if (i == len)
View
@@ -769,6 +769,8 @@ static char *(features[]) =
static int included_patches[] =
{ /* Add new patch number below this line */
/**/
993,
/**/
992,
/**/

0 comments on commit f6d9f96

Please sign in to comment.