On Dec 11, 2012, at 17:14 , Doug McNutt <[email protected]> wrote:
> 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! Heh. I thought I was showing my age (I remember those days very well and wrote drivers for plenty of printers back then that used those codes and other control codes). Greg
smime.p7s
Description: S/MIME cryptographic signature
