Mark Hammond wrote: > So we must work without effective EOL support? I fear we will end up > like the mozilla hg repo with some files in windows line endings and > some with linux. While my editing tools are good enough to preserve > existing EOL styles, I've found myself accidentally checking in new \r\n > terminated files in a repo which otherwise uses \n line endings. IMO, > SVN's EOL support was better than no EOL support.
If Mercury doesn't have automatic whitespace conversion along the lines of svn:eol-style, then the existing white-space checking script probably needs to be updated to enforce the appropriate line endings for all files. If we default to Unix line endings for most files, then the checking script can be made aware of which files should always have Windows line endings (I believe the various Visual Studio files need them, batch files are probably best left with Windows line endings in the repository, and I expect there are other files in PC and PCbuild that need them as well). However, I expect that would still be painful to work with for Windows developers, even if it prevented any line ending problems from making their way into the main repository. I believe that is where the win32text extensions can help. Looking at the Wiki page for win32text [1], I believe it would be a matter of configuring the extension to encode and decode all files with the extensions: *.py *.pyw *.h *.c *.in *.rst *.asdl That said, I don't see a way to tell win32text to also translate files which don't have an extension at all (e.g. NEWS or ACKS), and there doesn't seem to be a way to tell it to *skip* files matching certain patterns (if there was, we could just tell it to ignore extensions like .bat, .sln, .vcproj, .vsprops, .dps, .dsw, .wse, .ico, .bmp and convert everything else) Cheers, Nick. [1] http://mercurial.selenic.com/wiki/Win32TextExtension -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia --------------------------------------------------------------- _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
