Notepad++ release 8.7.1

donho

Notepad++ release 8.7.1 is available here:
https://notepad-plus-plus.org/news/v871-released/

Notepad++ release 8.7.1 change log:

Update cURL in Notepad++ updater (WinGUp) for fixing cURL’s CVE-2024-7264 issue. (Fix #73)
Fix opened network files hanging while the network disconnected. (Fix #4306, #6178, #8055, #11388, #12553, #15540)
Fix not being able to open folder via cammand argument regression. (Fix #15645)
Update to Scintilla 5.5.3 & Lexilla 5.4.1. (Fix #15228, #15368, #15650)
Fix modified Find dialog status msg colors not being remembered throu sessions. (Fix #15724)
Fix hanging issue while hiding lines. (Fix #15630)
Make left behide hide line close marker removable. (Fix #15713)
Fix Find dialog status bar wrong messaging (regression). (Fix #15662)
Fix URL parsing issue with ‘?’ after ‘#’. (Fix #13583)
Add “Close to system tray” ability. (Fix #4075, #11627)
Add tab created time tooltip for new opened untitled tab. (Fix #15563)
Improve GUI to avoid user confusion between Global override & Default Styles. (Fix #15640)

Auto-update will be triggered in one week if no critical issue found.

schnurlos

https://notepad-plus-plus.org/downloads/v8.7.1/ release date is wrong

donho

@schnurlos said in Notepad++ release 8.7.1:

https://notepad-plus-plus.org/downloads/v8.7.1/ release date is wrong

I could be in one of Asian countries so the release date could be correct…
OK, I’m in Europe. Fixed :)

PeterJones

@donho said in Notepad++ release 8.7.1:

I could be in one of Asian countries so the release date could be correct…
OK, I’m in Europe. Fixed :)

Not fixed yet:

This month is November (11), not October (10). I think that was @schnurlos’s quibble, not the 5th vs 4th.

donho

@PeterJones said in Notepad++ release 8.7.1:

@donho said in Notepad++ release 8.7.1:

I could be in one of Asian countries so the release date could be correct…
OK, I’m in Europe. Fixed :)

Not fixed yet:

This month is November (11), not October (10). I think that was @schnurlos’s quibble, not the 5th vs 4th.

Oups, thank you @PeterJones for the further explanation.
Thank you @schnurlos for remind me this important error.
It’s fixed now for sure.