Display line endings, line by line, like in Scintilla

[skuroda]

The reason to want to see both CR and LF is if I may be reading some wierd file that was maybe created-edited with a mixture of buggy Unix and Windows editors so that the file might contain a mixture of CR-LF and CR or other line endings structures. It is sometimes nice to see what is exactly going on with the file.

But isn't this not really an issue since ST saves the entire buffer with the specified line ending anyways? You could mix the two, but upon save, all line endings will be the same (whatever is specified). Or maybe I am missing something?

[bmanam]

+1 here too. I have it on almost permanently in Notepad++ & am tired of switching back and forth just to verify the line endings for files sent to me that have been created on Linux.

[bizoo]

+1 here too. I have it on almost permanently in Notepad++ & am tired of switching back and forth just to verify the line endings for files sent to me that have been created on Linux.

Did you read the previous post ? What do you want to verify ?
You can check the line endings in the menu View -> Line Endings.
And there's no mixed line endings in a view, ST normalize them when loading the file.

If you want to mix line endings in a file, you must use another editor.

[bmanam]

Alright then. Leaving aside the fact that an option would reside in the view menu which has no visual effect when changed, I'll put this one to bed. Automatic normalization of line endings will do.

[bizoo]

Alright then. Leaving aside the fact that an option would reside in the view menu which has no visual effect when changed

Take a look at https://github.com/SublimeText/LineEndings
Also available at Package Control.

[chief1983]

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.

[facelessuser]

This could be coded up in a plugin. You could run the command on a view, and the view would be manually reloaded showing all carriage returns. While in this raw line edit mode, you could look at the line endings and enter new ones: maybe enter gives you unix, and shift+enter gives you windows style. I have a plugin locally on my machine that can do this (the user interface needs a little work), but if you are interested, I may try to revive it and hammer out the issues to make it usable. It would currently be for ST3. Anyways, just thought I'd share.