In another post, I mentioned that I had extended TranscriptTTY with a #lf method that sent a line feed. I did this because when using TranscriptTTY and sending it #cr there seemed to be extra carriage returns placed in the output. The text editor I use displays these extra Cr's in an anoying way that I can't seem to turn off.
I checked into this a little further and found that sending a LF character to TranscriptTTY results in putting a Cr and Lf in the output. The #cr method sends the CldtConstants::LineDelimiter string (which is a Cr and Lf on windows) and results in two Cr's and a Lf being put in the output. I think (a guess on my part) that this is a problem with the VM as the code that sends characters and strings to TranscriptTTY with #outputToTTY are primitives.
This isn't a big deal, so the developers shouldn't worry too much about it on my part. If anyone else has any other ideas, I'm at least mildly interested.
P.S. If you can run this in a server (not the development environment) you can see what I mean.
- Code: Select all
tty := TranscriptTTY default.
tty show: 'LineDelimiter size: '; show: CldtConstants::LineDelimiter size printString; cr.
tty show: ('xxx', CldtConstants::LineDelimiter, 'xxx'); cr.
tty show: ('yyy', CldtConstants::Cr asString, CldtConstants::Lf asString, 'yyy'); cr.