+1 from me also. I need to know clearly if there is a CR vs CR LF. I use text editors to view and manipulate data files quite often, and the distinction is significant. Scintilla displays them exactly like Notepad++ and that's precisely what i need.

If you don't want these displaying permanently then you could just use Find and Find All using the regex '\n' and/or '\r\n'. This allows you to scroll up and down but, of course, you could use Replace as well.

While this may be possible via a plug-in I suspect it will muck up all the scoping rules.

Attachments

newline.png (20.63 KiB) Viewed 14582 times

"I'm here to save your life. But if I'm going to do that, I'll need total uninanonynymity." Me Myself & Irene.

As of now, I don't think this can be done (even via plugin). From what I have seen, and a quick search of the issue pointing me here, Sublime Text normalizes line endings to "\n" when the file is loaded (I verified this as a file I created with "\r\n" did not contain any "\r" characters when I did a regex find). When the file is saved, all line endings are converted to what ever is specified (or opened with). I tested this by creating a file containing both line endings, opening it in Sublime Text, making some modification and saving it. So good news, when you save in Sublime, all the line endings should be consistent, bad news, you can't actually see individual line endings.

I realize opinions differ on whether it is really needed to show carriage returns and line feeds, but really I am just showing that Sublime Text can technically show carriage returns. Line feeds seems redundant since you can see the line on the next line number, but again, opinions differ on this.

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.