[Updated] EditPad Lite..Ver..7.2.3..Feb.22/13
EditPad Lite is a general-purpose text editor, designed to be small and compact, yet offer all the functionality you expect from a basic text editor. EditPad Lite works with Windows 98, ME, NT4, 2000, XP, Vista, and 7.
Ignore command line parameters pointing to notepad or notepad.exe.
Preferences, Search: Turning off "double-clicking a word instantly highlights all occurrences of that word" and clicking OK in the Preferences window now removes any instant highlighting so users who are unaware of the Search|Instant Highlight menu item don't get stuck with a highlight they're trying to disable.
File|Rename/Move: Renaming files now works even when the only change is a difference in case.
Keyboard: Ctrl+punctuation key combinations to type letters with diacritics did not work if the punctuation key is typed by a Shift+number key combination, even after removing the same Ctrl+Shift+number key combination from the shortcuts for the Mark menu.
Preferences, Search: "Double-clicking a word instantly highlights all occurrences of that word" now only invokes Search|Instant Highlight when you actually double-click a word, and not when you double-click something else that has a double-click action of its own, such as URLs that open web pages. Selecting Search|Instant Highlight in the menu will still highlight whatever is selected or under the cursor, even if it has a double-click action.
Search commands that process all matches like Replace All showed an access violation error after showing a proper error message when attempting to use an invalid regular expression (7.2.1 and 7.2.2 only).
Search: Replacements that include placeholders like %MATCHN% were made as if the "Adapt Case" option was always on when the "Regular Expression" and "Case Sensitive" options were off.
Search: Replacements with double-digit backreferences starting with a zero like \06 were interpreted as \0 only instead of \0 followed by a literal digit (e.g. 6) if there are fewer than the specified number (e.g. 6) capturing groups in the regex.
Search: Searching for a regex with a syntactically invalid character class containing a hyphen such as [\u1234-\u567] and then searching for a syntactically valid regex containing a character class caused the regex to be parsed incorrectly, adding a literal hyphen to the character class. Any subsequent searches using another regex with only valid character classes had the regex parsed correctly again.