You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Крас\x1bниво only Крас is processed with input, while rest terminals(vte, xterm) output Красиво. On the other side Hello\x1bworld will process with inputHello and orld only consuming w.
The text was updated successfully, but these errors were encountered:
I've looked into this a little bit and the solution is likely to move the unicode parser table definitions from the Ground state to the Anywhere state.
I'd have to think a bit more of the concrete implications, but I don't think unicode is valid as part of any escape sequence? Though Alacritty certainly accepts in right now for URLs for example.
When using
Крас\x1bниво
onlyКрас
is processed withinput
, while rest terminals(vte, xterm) outputКрасиво
. On the other sideHello\x1bworld
will process withinput
Hello
andorld
only consumingw
.The text was updated successfully, but these errors were encountered: