This is similar to a vim error, in particular an error with vim internal escape sequences that begin with \x80(the second byte of the corresponding character \x80) and encodes various things, such as NULL, function keys, or \x80itself. I think you can delve into the vim source code and find out how this byte is escaped, and try to replace the last byte ‘with this escape code or wait until it is fixed (although I will not expect a correction to come soon : here is a quote from todo.txt
UTF-8: multibyte key mapping, where the second byte is 0x80, is not displayed to work. (Tony Mechelink, 2007 March 2)
So, you see that the problem has been known for four years and has not yet been fixed.)
source
share