Notepad++ v8.8.6 Release
-
Notepad++ release 8.8.6 is available:
https://notepad-plus-plus.org/news/v886-released/Notepad++ release 8.8.6 virus scanner issue? Please check the following link:
https://notepad-plus-plus.org/news/v883-self-signed-certificate/Notepad++ v8.8.6 new features & bug-fixes:
- Add capacity of pasting multiline into Find/Replace fields. (Fix #16952)
- Improve UAC in Notepad++ for seamless elevated operations. (Fix #886, #8655, #9561, #10302, #14990, #15008, #15137, #15323)
- Fix Pin Tab operation being too long with many opened documents. (Fix #16117)
- Add 2 new full-readonly modes via command line argument (-fullReadOnly & -fullReadOnlySavingForbidden). (Fix #15993, #16532)
- Add apply/remove read-only for all documents commands. (Fix #15993, #16532)
- Column Editor enhancement: GUI input fields now support radix to match the output format. (Fix #16912)
- Add Window dialog “File Modified Time” sorting capacity. (Fix #16953)
- Fix NPPN_CMDLINEPLUGINMSG not working issue & define the pluginMessage usage protocol. (Fix #17024, #17022)
- Fix pasting from column mode to multi-selection issue due to different EOL. (Fix #16889)
- Add NPPM_GETNPPSETTINGSDIRPATH message to get Notepad++ settings directory path. (Fix #16944)
- Enhance SQL function list parser. (Fix #16605)
- Fix C# function list not working with comments. (Fix issue)
- Add function list ability for CSS. (Implement #17006)
- Allow user to customize max selected chars to auto-fill “Find what” field. (Fix #16955)
- Restore undo/redo behaviour in Find/Replace fields after Copy/Paste or Ctrl-F. (Fix issue 1, issue 2)
- Fix text corruption issue caused by selection within multibyte characters. (Fix #16879)
- Fix DOCTYPE styling in xml and html. (Fix #17012)
- Fix double clicking on edit zone’s border creates a new tab issue. (Fix issue)
- Update cURL in WinGUp (Notepad++ updater) for fixing CVE-2025-5399. (Fix security issue)
As usual, auto-updater will be triggered in one week, if no critical issue found.
-
P PeterJones forked this topic on
-
@donho ,
I am attempting to draw out the details, but it appears that “Enhance SQL function list parser. (Fix #16605)” may have caused a regression for some SQL function lists.
See, for reference, the discussion “v8.8.6 - the function list is not working”.
(I will update this post if I can get the poster to share example SQL syntax that had correct FunctionList under old and broken under new; right now, there are screenshots of the difference, but the screen doesn’t show the SQL syntax that’s defining the functions/procedures that aren’t being listed.)(I personally don’t think it’s worth stopping a trigger on auto-update for v8.8.6, as the workaround is as simple as putting a different sql.xml in the AppData\functionList, but it should be probably be tracked as a regression for this version, anyway.)
update: the “v8.8.6 - the function list is not working” discussion now has example SQL that shows the problem.
Unfortunately, it appears that it’s the old space-required-after-class-closing bug that’s never been found (it’s usually reported when there’s no space/newline after the closing
}
in a C++ or similar class). It didn’t show up in v8.8.5 and earlier, because the old SQL FunctionList parser definition didn’t include classes, just functions, so it was able to find the functions.The user has decided it’s easiest to just add the newline at the end of the files that don’t show up, and is happy.
update 2: the relevant issue is #2910, and all the ones that have been closed as duplicates of it
-
@PeterJones
Thank you for posting it & reminding me one more hard bug to fix :( - I’ll work on it ASAP. -
FYI: The auto-update will not be triggered for v8.8.6, since v8.8.7 will be released in 3 days:
https://community.notepad-plus-plus.org/topic/27193/fyi-notepad-v8-8-7-release-candidate-will-be-out-in-1-dayThis is because I received a new certificate issued by GlobalSign this afternoon:
Therefore, it makes sense to release a new version immediately after v8.8.6 to address the security issue & provide a better user experience.
PS. the self-signed certificate will be kept. The binaries will contain 2 signatures.