Just to mention, for people using Intune to deploy notepad++. if you activate the “managed installers” option, any apps not signed wil lbe signed with a valid certificate and therefore users don’t have popup for the “unknown publisher”. I think you can do the same with SCCM. Will not help regular users, but jsut in case.

Ref to Npp website spelling error

@donho said in Notepad++ v8.8 Release:

@Neymar44
The bug has been fixed in v8.8.1. Here is v8.8.1 RC:
https://community.notepad-plus-plus.org/topic/26833/notepad-v8-8-1-release-candidate

The glitch indeed disappeared in the last 8.8.1 RC, thank you !

Another regression has been found here:
https://community.notepad-plus-plus.org/topic/26815/notepad-v8-8-release/4?_=1746291034345

The regression has been fixed in the new binaries:
http://download.notepad-plus-plus.org/repository/8.x/8.8.1.RC2/

@schnurlos

https://notepad-plus-plus.org/news/v88-we-are-with-ukraine/ gives an Error 404 (link within “F1” Info).

It’s because v8.8 is still in RC state.
It will be on line in few hours.

2 off-topic posts are moved to:
https://community.notepad-plus-plus.org/topic/26793/all-the-off-topic-go-here

@mkupper
Thanks, those 2 links provide reasonable “guess-timates” re: what to expect in the next release.
Murray

@donho ,
That fixed that issue, thanks.

The unrelated post has been moved to 22917 of Boycott Notepad++.

Possible v8.7.8 regression: GitHub issue #16250 .

@xomx ,
Understood. I wouldn’t want to rush stability, but I agree with your assessment that it’s a straight forward fix that I don’t think would affect anything else but what’s intended, but I can wait if need be. Thanks again for the help with unraveling this while I was trying to find out the actual issue at the heart of the problem.

@Mark-Olson
Fixed. Thank you!

@Kaptain-Biwouak ,

It is up to each plugin’s author/maintainer to determine whether or not their plugin is affected.

Don, as the owner of Notepad++ but not of the plugins that are written for Notepad++, doesn’t have the bandwidth to review the source code of every plugin that exists for Notepad++ to determine whether or not it would be affected, hence he made this announcement to let the plugin authors know that they each need to check their own plugins.

addendum: and if users want to find out if any of the plugins they use are affected, they can just try the plugin(s) in v8.7.6, because what happened was that it was found that efficiency-improvements in v8.7.6 unintentionally broke some plugins by disabling some events; the changes that will be in v8.7.7 will allow plugins to use the API to ask Notepad++ to re-enable the mentioned events on a per-request basis.

So, if you are successfully using a plugin in v8.7.6, you can continue using it in v8.7.7. If you find that a plugin worked in v8.7.5 but broke in v8.7.6, then you could check the homepage for that plugin and see whether or not they’ve mentioned a fix or released a new version in the last week or so, and if not, then ask them if they will have a fixed version ready in time for v8.7.7.

@xomx

“…instead of unnecessarily burdening all the present plugins with unsolicited notifications (for most of them), it would be better if plugins that want something like this, actively request (registered somehow?) that info being sent only to them by the N++.”

Indeed, it (adding a new API) will be the better solution than keeping all events of SCN_MODIFIED notification ON for some plugins which don’t need the all these events, or even for users WITHOUT any plugin.

In the worst case, users get all the plugins which need ALL the events of notification SCN_MODIFIED and the performance will be equal as the old configuration (v8.7.5 and former versions), not worse.
But in the most cases, the performance will always be better than before.