© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
Here's what xterm is apparently seeing when I scan a barcode and use the -l option to log the output.
^[]0;isisup@
The 1G is the first 2 printed characters of the barcode in this case, but there are 15 more it should have kept reading instead locking up.
Using another barcode I get this:
^[]0;isisup@
The 3B5 is actually incorrect in this case, the barcode I scanned is should be showing 3B7 then another 14 characters.
Now I tried the same thing on the older version of xterm and it also has the same control characters in the log to start with, but will finish scanning the full barcode to the command line. Any ideas on this?