Skip to content

Commit

Permalink
fix typo in link
Browse files Browse the repository at this point in the history
  • Loading branch information
pryrt committed Feb 10, 2025
1 parent 146b44e commit b8b9e50
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/docs/preferences.md
Original file line number Diff line number Diff line change
Expand Up @@ -371,7 +371,7 @@ Defines whether or not to perform saving sessions, periodic backup, and backup o
* For _named_ files (existing or saved files that have recent edits) the name of the backup file (in the listed directory) is `filename.ext@yyyy-mm-dd_hhmmss`, where `filename.ext` is from the main file. As soon as you manually save the file (so it’s written to disk in the real location), the backup goes away, because the purpose of the periodic backup is to save a copy of a file that you’ve edited but not saved. The timestamp part of the periodic-backup-name is based on the first automatic save after the last manual save. Example: if you saved a file at 8:10:00am, the backup would go away; then, at 8:12:30am, you type something but don’t save, so sometime within N seconds of that (8:12:30+N) it will periodic-backup-save and make a file with a timestamp about then – something like `filename.ext@2021-06-23_081234`. If you left for a while (or exited Notepad++ and reloaded) and came back at 12:34:56pm and typed another character, it would do it’s periodic-backup-save on that file again so the last-modified time of the backup would be updated), but the name of the periodic-backup file will remain the same.
* For _unnamed_ files (new files that haven't been saved) the name of the backup file (in the listed directory) is `new NNN@yyyy-mm-dd_hhmmss`, where `new NNN` matches the name listed in the tab title. Since `new NNN` files are by definition not manually saved, the timestamp in the periodic-backup filename is based on when it did the first periodic-backup-save for that unnamed file.
* **WARNING**: The Notepad++ periodic backup feature in multi-instance setups will work only for the first Notepad++ instance; there will be no periodic backup for subsequent instances.
* `☐ Remember inaccessible files from past session`: Changes the behavior of how Notepad++ handles files that don't seem to exist when Notepad++ loads the session. With the option checkmarked, sessions can remember files even if they don't exist any more, based on your reply to a dialog box; if it is not checkmarked, sessions will not remember missing files. There is more about this behavior documented in [Sessions > Inaccessible Files](../sessions/#inaccessible-files). (New to v8.6.)
* `☐ Remember inaccessible files from past session`: Changes the behavior of how Notepad++ handles files that don't seem to exist when Notepad++ loads the session. With the option checkmarked, sessions can remember files even if they don't exist any more, based on your reply to a dialog box; if it is not checkmarked, sessions will not remember missing files. There is more about this behavior documented in [Sessions > Inaccessible Files](../session/#inaccessible-files). (New to v8.6.)
* **Backup on save**
* `☐ None`: No additional backup will be performed when the file is saved.
* `☐ Simple backup`: It will save a copy of the file, with the same name and extension, but with `.bak` appended.
Expand Down

0 comments on commit b8b9e50

Please sign in to comment.