notepad-plus-plus / notepad-plus-plus/notepad-plus-plus
Problem with backup
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29.4k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Notepad++ is realy great and usefull tool, which I use in many cases.
And one of most usages is as its name says -- I use it as notepad.
In my case, I usually have an unsaved session, consisting of unsaved files.
But an unfortunate situation arose (I lost the text I worked on for 4 days):
I closed an unsaved file in session and its backup-file disappeared from the backup folder.
Description in screenshots for clarity:
For example, I have a session with an unsaved file ("new 1" in example).
-- its backup in the backup folder.

The problem is that when I close "new 1" in Notepad++ session, backup of "new 1" in backup folder will be lost too.

If I close Notepad++ (application) (with some unsaved files like "new 2", "new 3" opened) backup files will keep saved in backup folder.

Behaviour varies.
I would like to make it to:
(Automatically) save backup files (in the backup folder) even of unsaved files that was closed in the session.
This will probably increase the number and size of backup-files in the backup folder, so this might be optional.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported sequence with an unsaved session: close one unsaved file, then inspect the backup folder, and compare it with closing the application while other unsaved files remain open. Trace the session and backup handling entry points responsible for file closure and shutdown. Done means closed unsaved files retain backups, with any optional behavior reflected in the issue's requested setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100