Is this a concern or a false positive?

Thanks.

The “Notepad++ vX.Y.Z Release” topics in the Announcements section isn’t the place for feature requests; these discussions are focused on reporting regressions (things that used to work but don’t work in a new version, or new features that were added in X.Y.Z that are broken immediately).

If you want @donho to see a feature request, you should go to the GitHub repository issues tracker and make your request there. If you want to talk it over with the Notepad++ community here first, then you can post in Help Wanted or General Discussion, where the fellow Notepad++ users can help give you advice, and help flesh out the idea before you put in the feature request. (See our FAQ about feature requests.)

(Personally, I disagree with your feature request: the backup files should be an exact copy of the file, otherwise it’s not a backup. The name and path and date-of-save are literally stored in the name of the backup file, so there’s no reason to put that information in the file contents as well. But this isn’t the right location for such discussions.)

/*

• Name: test.txt
• Path: D:/user/test/
• Date of saving: 2025-09-15 21:54:33
• Date of change: 2025-09-17 15:21:12
  */

File Contents…

I got it updated since I check before I go to bed. :-)

Quick question. Did 8.8.5 update get triggered? I’ve been checking to see if my Standard install can be updated and it keeps saying there is no update, so did it get delayed, or am I missing something?

Oups! I forgot it!
Thank you for your heads up. It’s triggered now.

Actually, the following code in Notepad_plus::doReload seems to be related to activating the buffer, so I’m not sure what actually happens:

if ( ((currentView() == MAIN_VIEW) && mainVisible) || ((currentView() == SUB_VIEW) && subVisible))
{
activateBuffer(id, currentView(), true);
}

What happen is exactly as its comment:

	// Once reload is complete, activate buffer which will take care of
	// many settings such as update status bar, clickable link etc.

:)

If there is a new version available, it may not have been triggered for auto-update yet. In order to avoid to spreading a new version which contains regressions or critical bugs, we wait for users’ feedback before triggering the auto-update, often one to two weeks. If a critical bug or regression is found, the auto-update will not be triggered for that release. On the other hand, after a reasonable delay, if we are confident there are no critical issues, the auto-update will be triggered. This safety delay prevents bad bugs or regressions from being widely spread throughout the Notepad++ user-base, limiting the exposure to those users who are watching for release announcements and are willing to manually upgrade Notepad++.

This is mentioned here: https://npp-user-manual.org/docs/upgrading/#new-version-available-but-auto-updater-find-nothing

if ( ((currentView() == MAIN_VIEW) && mainVisible) || ((currentView() == SUB_VIEW) && subVisible))
{
	activateBuffer(id, currentView(), true);
}

Looks like the behavior of NPPM_RELOADFILE has been changed in either 8.8.5 or 8.8.4.

I don’t think so.
Here is git blame for the API you’re talking about:

Obviously, the latest changing is the last year. So it was not changed in v8.8.4.
BTW, you’re the only one (AFAICT) who complains this problem.
If you find any issue, you’re welcome to create an issue on GitHub, and ping me - I’ll check it.