Syntactic Confectionery Delight | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
You mentioned something about an "Xemacs shell". Is that a variable that can be eliminated? In this case the xemacs shell was being used as a control rather than something to be eliminated. One way of assuring myself that this was xterm specific behavior was to run the script in an alternative shell and see what happened. As it turned out, there was no disappearing output in the xemacs shell (which is really just a file buffer pretending to be a shell). I also dumped the output to a file instead of the terminal (as suggested above by BrowserUK and not surprisingly it was all there - no disappearing output. This really does seem to be an xterm problem. those normally start with ESCape (^[). Like you, that was my first assumption too, but googling around I see that there does appear to be some overlap between UTF-8 and xterm escape sequences. For example, Under normal mouse mode, positions outside (160,94) result in byte pairs which can be interpreted as a single UTF-8 character; applications which do treat their input as UTF-8 will almost certainly be confused unless extended mouse mode is active. Source: http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#Mouse%20Tracking I'm not sure how that explains what I'm seeing, but that may not be the only case of overlap. I don't know much about terminals, and less about xterm. I didn't even have xterm installed until this came up. Wow. Many thanks for the effort you have put into this! In reply to Re^4: Printing the first letter of the Hebrew alphabet (U05D0) kills script?
by ELISHEVA
|
|