At 21:00 -0800 12/10/12, Gregory Shenaut wrote: >It seems to me that a file with mixed line endings should be interpreted such >that \r sends the carriage back to first column but doesn't advance to the >next line, with \n serving to move down one in the same column: in other >words, a file intended for a printer. In that world, only DOS-style \r\n will >work as a line-end per se. Or, to generalize this a little, in a file >containing both \r and \n characters, those characters should assume their >ASCII significance, with \r\n counting as a line ending. In files with \r but >not \n, use \r as line-end; in files with \n but not \r, use \n as line-end.
You're showing your youth! I can remember a time when those line ends did exactly what you say. The machine is called an ASR33 teletype or, later, a Flexowriter (TM) where you could personalize letters to lots of people.. One could send a CR and retype the same line. That allowed for a version of bold emphasis or a way to make a phi out of an O by adding a / character on the second pass. You could also underline stuff. An interesting feature was that one needed to send returns and line feeds in the right order for the destination machine and some nulls were needed to allow for the required motions to occur before the next character to be printed. Other control characters, pretty much ignored today, were used to shift to upper case or to numerics with 6, or even 5, bits per byte. What was really fun was sending lines to a Control Data line printer where you could have a whole line reprinted as many times as you want before sending a line feed. I still have a calendar for something like 1965 that includes the Playboy centerfolds done that way. The code depended on carefully worked tables of the density of overprinted pairs of characters. My machines expect RS232 line feeds and returns and do things like that today. BBEdit just cannot be used. Perl is the way to go but don't even think about debugging code with BBEdit as the viewer for the output as well as for the source code being edited.. And. . . Do you know that, in the Apple world \r is supposed to be equivalent to 0A and \n is a 0D? That was observed in the day when MPW was the way to go but it made it into some IETF standards and hasn't been removed even though OS neXt with it's NEXT, Inc origins doesn't follow that standard. -- --> Halloween == Oct 31 == Dec 25 == Christmas <-- -- -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
