I didn’t observe such issues with this version of N++. I’m using a similar configuration except of NppExec. Which version of NppExec do you use? 0.6 beta1?

I often think when it comes to computers and software, that if I come across a problem or in this case a “design behavior” as you call it, I’m not alone. :D
So I think of keeping the “Find” window open as an improvement and more users than me would find it useful.

Best regards

Get the answer,inspired and trying.

In the newest version, it’s not enough to delete all the .xml files in C:\Users\X\AppData\Roaming\Notepad++.
You must delete files in C:\Users\X\AppData\Roaming\Notepad++\backup as well.
Then just restart.

Very useful! Thank you!

Unfortunately, you’re not alone. Comptuer crashes can cause unexpected behavior, and so far, no one in the development team has been able to reliably replicate and thus debug how to prevent the problem. This is officially tracked in issue #2381

Regarding the specifics of your instance: you mentioned checking in %AppData%/Notepad++/plugins/config/NppFTP/Cache… but that’s only used to cache files if you’re using the NppFTP plugin to edit remote files (on your webserver, or similar). The right directory location for Notepad++'s backup (assuming you have Settings > Prefrences > Backup enabled) would be %AppData%\Notepad++\Backup: did you check there? Also, if you used a “local”/portable version (check ? menu > Debug Info, and look for “Local Conf mode:”; if it says ON, then it’s “local”), then the backup directory would be a subdirectory of your whatever directory notepad++.exe is in, rather than in the %AppData% hierarchy.

Unfortunately, if it’s not there, there’s probably not much we can do to help you recover it. However, you’re luckier than some, if your statement that “whatever data I had saved till yesterday is also fine” means that you did have your own backup somewhere, and that you’ve just lost the most recent edits. (If not, for the future, I highly recommend that you keep a backup of any important data**. This can be done with dedicated backup software, or with storing your files in a service like dropbox or one drive or google drive or similar. Or using version control software, such as git or subversion.)

History:

Back in December 2017, @chcg summarized the history of the topic up to that point: https://notepad-plus-plus.org/community/topic/14945/rare-null-write-glitch/2, which @Scott-Sumner updated in January (https://notepad-plus-plus.org/community/topic/15112/attempt-to-recover-files-after-npp-blank-2-files-after-error-missed-the-error-msg/2)

Since then, there have been at least a few more posts on the issue in this forum (incomplete):

https://notepad-plus-plus.org/community/topic/15549/help-my-pc-crashed-while-editing-and-deleted-my-whole-document/2 https://notepad-plus-plus.org/community/topic/15531/nul-nul-nul-problem-notpad

In March, I posted (https://notepad-plus-plus.org/community/topic/13302/fix-corrupted-txt-file-null/19) that I’d tried to force Windows to crash, but no matter what I did, I could not replicate the NUL-file issue. And @Scott-Sumner had tried the same thing some time earlier, as he revealed in the next post, with the same could-not-repeat-it results). This is a difficult issue to debug, and until someone steps forward with a reliable method of repeating it, it’s probably not going to get fixed.

@Herb-Martin

Many thanks Herb-Martin for your suggestion. Much appreciated.

Can’t figure out what you want to replace exactly (from the description) but based on the title and general idea I 'll give an example that you might modify to achieve your real goal:

I want to find lines starting with abc and change MISTeak later in the line to CORRECTED without changing anything else, using Replace dialog with Regular expresions:

Find: ^(abc.*)MISTeak

Replace: $1CORRECTED

^ start of line match only
( ) parens “capture” whatever is between them, you must write ( or ) if you need to match a real paren
abc – match literally abc
.* any characters, as many as are found including NONE.
MISteak : those literal characters (can be marked case sensitive or not)

$1 replace what you found in FIRST paren set, if you had () and () the $2 would be 2nd capture etc.

Save your doc, try it, use undo if you make a mistake and if you seriously foul it up reload the saved doc from disk.

Weakness (which can be fixed): What if MISTeak appears more than once in the line – there are ways to fix that too.

Two ideas:

If you have Line numbers enabled then clicking out there selects an entire line and allows you to easily drag mark multiple lines.

I didn’t know that until trying to answer your question so thanks for helping me learn something.

When I select in the FIRST column and drag it marks lines – it’s easy to mark just on line that way or a long section, but then thatn’s the way I have been doing it for years, maybe decades (How long has NP++ been around?)