I end up using it like a glorified sticky tool which I know windows did have at some point, but Notepad++ provides the same functionality with a much better experience.
Several years ago I tried loads of "lightweight" graphical text editors for Windows, searching for something with fast start-up and ability to load (and edit) humongous text files. Been using PSPad back then, with NPP as a side-kick, but when it came to dealing with super large files, this editor came as the most performant and reliable. It's data and memory footprint is super tiny and is quite extensible.
I've never used it as a primary editor so cannot speak much about features (yes it seems dated and configurations seems wonky) but really proved to be workhorse for me.
(Nowadays I mostly live in VSCode but still keep this AkelPad (and Foxe [1] / First Object editor for XML files) around when necessity to deal with something huge arises.)
[0] http://akelpad.sourceforge.net/ [1] http://www.firstobject.com/dn_editor.htm
It has several modes (normal, regex, normal-with-multiline) so you can always choose easily the one that fits your scenario. The multiline one is IMO pretty useful - it allows multiline but allows to avoid clunkiness of regexes and escapings.
(It also hangs on opening a 500 MB file, too. Version dialog just gives me my Win10 version.)
there is a difference?
If you open a (small) image file with notepad you will see a lot of gibberish. This is what happens when you try to view a binary (in other words, non-text) file as text.
But if you're saying it's not included in Windows 10 it might be a sysinternals branch.
The error is cute:
> The test_1073741824_bytes.txt file is too large for Notepad.
> Use another editor to edit the file.
followed by:
> The operation completed successfully.