Submitted via IRC for TheMightyBuzzard
For many years, Windows Notepad only supported text documents containing Windows End of Line (EOL) characters - Carriage Return (CR) & Line Feed (LF). This means that Notepad was unable to correctly display the contents of text files created in Unix, Linux and macOS.
[...] Starting with the current Windows 10 Insider build, Notepad will support Unix/Linux line endings (LF), Macintosh line endings (CR), and Windows Line endings (CRLF) as usual. New files created within Notepad will use Windows line ending (CRLF) by default, but it will now be possible to view, edit, and print existing files, correctly maintaining the file's current line ending format.
It's about damned time.
Source: Introducing extended line endings support in Notepad
(Score: -1, Troll) by Anonymous Coward on Saturday May 12 2018, @07:06PM (2 children)
Riiiiiight. So why is there still a Notepad and a WordPad and why have the two programs not been merged into one program by now.
Why if you care about line endings are you not using WordPad anyway?
Oh I get it. Uzzard is a fucking moron.
(Score: 0) by Anonymous Coward on Sunday May 13 2018, @01:21AM (1 child)
Well, it's not that hard to understand. Notepad only handles plaintext. WordPad handles RTF as well as plaintext, tough Notepad is better for plaintext.
The right tool for the right job.
(Score: 4, Informative) by Nerdfest on Sunday May 13 2018, @02:57AM
To be fair, neither are really the right tool for any job.