Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Non-ASCII text issue
See original GitHub issueOS: Windows 10
In hterm mode, If I type non-ASCII(Korean) text in the terminal, it appears bottom or top of the screen and doesn’t disappear.
In xterm mode, there is no issue like above but non-ASCII text is displayed with black color, so it is hard to distinguish.
I think xterm mode is better, except #755 and this text color problem. Please allow to change color of non-ASCII words.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Error: There are non-ASCII characters in the local part of the ...
If you receive the following error when sending: There are non-ASCII characters in the local part of the recipient address, you are probably...
Read more >Check for non-ASCII - cs.wisc.edu
Choose a file to check for non-ASCII characters: OR Copy/paste your code here to check for non-ASCII characters:
Read more >Issue with Non-ASCII Characters in R - Stack Overflow
I am loading data in R with free-text fields that have a variety of non-ASCII/double byte ...
Read more >How to Find Non-ASCII Characters in Text Files in Linux
In this tutorial, we'll look at some tools to find and highlight non-ASCII characters within text files.
Read more >Reading non-ASCII text — Aldebaran 2.4.3.28-r2 documentation
Notice at last that regardless of the file encoding, everything gets encoded to 'UTF-8' before being sent to the text-to-speech proxy. Running the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
xterm issue is likely because of
3.13.0-beta1’s issue.try creating issue at the xterm.js.
build results of master branch (xterm == 3.13.0-beta1)
build results of modified version of master branch
(xterm version of terminus-terminal was modified to 3.12.2)
Fixed in xterm