I registered here, just to give the use case I commonly run into for needing to see line endings. If you don't already know why this is important, and why I have to keep Komodo Edit around on OS X, then you've probably not done a lot of cross-platform development involving patches before. I work with a Windows/OS X/Linux project, and there are patch files created by TortoiseSVN users, *nix command line SVN users, etc. Most of the files in the repo are forced to LF, but the project files for Windows are all CRLF endings, and occasionally a new file gets committed and doesn't get a propset applied to force it to LF because Windows coders ain't got time for that. So you then end up with large patches that have a mix of LF or CRLF in the diff-specific lines, as well as in the content. Command line diff tries to remove all trailing CRs if it thinks they're only there because the diff came from Windows, but if some of those files were also Windows files, it just ruined their diff. My point is, as far as the diff utilities are concerned, these mixed ending files are completely valid, and a text editor capable of displaying them exactly as-is is not only helpful, but required for working with them at times. I'd like to stop having to fire up Komodo every time I need to edit one. If ST is going to trash that data just by opening and saving a patch file, then it's useless to me for viewing/editing patch files and I'll have to keep Komodo around. It's still looking to replace Aptana as my PHP development environment though.