Guido van Rossum wrote: > On 8/13/07, Russell E Owen <[EMAIL PROTECTED]> wrote: >> In article <[EMAIL PROTECTED]>, >> "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: >>> I have run into files that intentionally have more than one newline >>> convention used (mbox and Babyl mail folders, with messages received >>> from various platforms). However, most of the time multiple newline >>> conventions is a sign that the file is either corrupt or isn't text. >> There is at least one Mac source code editor (SubEthaEdit) that is all >> too happy to add one kind of newline to a file that started out with a >> different line ending character. > I've seen similar behavior in MS VC++ (long ago, dunno what it does > these days). It would read files with \r\n and \n line endings, and > whenever you edited a line, that line also got a \r\n ending. But > unchanged lines that started out with \n-only endings would keep the > \n only. And there was no way for the end user to see or control this.
I've seen it in Scite (an editor based around Scintilla) just yesterday. It was rather annoying, since it messed up my diffs something awful, and was invisible to the naked eye. (But it lets you "Show Line Endings", which quickly made the problem apparent.) Later, Blake. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
