Feature/improvement suggestion

[Adam Narkiewicz]

I often do following steps:

1. Open multiple files from HDD in Notepad++ and work on them.
2. Upload the files to the server.
3. Delete the files from my HDD while they are still open in Notepad++.
4. Do File->Close All in Notepad++.
5. Then I receive a prompt: “The file XYZ doesn’t exist anymore. Keep this file in editor?” To see what happens, I click “Yes.”
6. All files get closed.

There are two problems here:

1. After asking whether to keep a file in the editor, Notepad++ closes it no matter what my answer is.
2. After selecting “Close All” Notepad++ asks me whether to keep some deleted files open, but not all (e.g. I have four files open, all of them deleted and I get only one such question).

This is not particularly annoying but I thought I would share it here because it seems there are some flaws in the application logic.

[PeterJones]

@Adam-Narkiewicz ,

(sorry for the slow reply: when I first read your post, I was in the middle of something, and couldn’t go looking for the issues, so I hoped that someone else would reply with similar information. Since no one has, I am doing it now.)

Honestly, I believe the bug is in step 5: it shouldn’t do that “check for underlying file existence” when you tell it to Close All (or when just closing one file, as in Issue #11866; or when you tell it to reload a file, as in Issue #18718). The developer tried (per this comment) to find a way around this, but hasn’t found a viable solution yet.

After asking whether to keep a file in the editor, Notepad++ closes it no matter what my answer is.

For me, since you already said “close all”, I don’t see a problem in Notepad++ closing it. I am not convinced it should’ve asked in the first place.

Fortunately, if there are unsaved changes – so if you’ve edited the file, so there are unsaved changes to the file that doesn’t exist anymore – it will interrupt the process and ask you to save it, and when it fails, it stops the process (not the best solution, but better than losing data). So this oddity at least won’t let you lose unsaved changes accidentally when doing Close All for files that have disappeared. So that’s something.

asks me whether to keep some deleted files open, but not all

That does seem problematic, to me. I guess after doing the single check, it finally believes your request to Close All meant to Close All.

---

In conclusion: Since Issue #11866 exists for the single file-close, I don’t think this needs a separate official issue. I’m glad it’s “not particularly annoying” to you, because it could be a long time (if ever) before a solution can be found.