Notepad++ v8.9.1 Release
-
FYI: Auto-update will be triggered for this release in one hours.
-
Auto-update is triggered for v8.9.1.
Note that auto-update doesn’t work when updating from v8.8.9 to v8.9.1 or later versions.
Version 8.8.9 will download the installer, but it will not launch the v8.9.1 or any newest installer, because v8.8.9 attempts to verify the old Notepad++ auto-signed certificate (which was removed since v8.9) instead of GlobalSign’s certificate. -
@donho
I went to the trouble to verify the signature before installing. I got this which includes a warning. Note, first time verifying sig using gpg, so maybe I got something wrong but I don’t think so.PS C:\Users\malaw\Downloads> gpg --import .\nppGpgPub.asc
gpg: key 6C429F1D8D84F46E: 56 signatures not checked due to missing keys
gpg: key 6C429F1D8D84F46E: “Notepad++ don.h@free.fr” not changed
gpg: Total number processed: 1
gpg: unchanged: 1
PS C:\Users\malaw\Downloads> gpg --verify .\npp.8.9.1.Installer.exe.sig
gpg: assuming signed data in ‘.\npp.8.9.1.Installer.exe’
gpg: Signature made 01/26/26 06:25:43 Pacific Standard Time
gpg: using RSA key 14BCE4362749B2B51F8C71226C429F1D8D84F46E
gpg: Good signature from “Notepad++ don.h@free.fr” [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
14BCE4362749B2B51F8C71226C429F1D8D84F46E
PS C:\Users\malaw\Downloads>So, good that it said good sig. Bad that key is not certified with trusted sig.
-
@A-T said in Notepad++ v8.9.1 Release:
Bad that key is not certified with trusted sig.
That just means that you haven’t marked it as trusted. GPG relies upon you to decide whether you trust a public key or not. If you don’t certify it as trusted, it will always say that it’s not signed with a trusted key, even though it confirms that it was signed with the key that it said it did.
-
Hi, for some reason it seems that in the INI and Properties languages Notepad++ now displays text before a
:in italics. After downgrading Notepad++ it seems this started in v8.8.9. I should also mention that fixing it after downgrading requires any customized themes in%appdata%\Notepad++\themesto be deleted or presumably fixed by hand.Example:
-
-
@mpheath said in Notepad++ v8.9.1 Release:
I am unsure what you fixed.
@mpheath, the user had outdated themes, which didn’t have the KEY style for either Langage:INI or Language:Properties. When v8.9.1 brought in all those style entries for the INI and Properties lexers, it began properly formatting those styles rather than ignoring those styles that weren’t defined in the themes. This was the intention of the new style-updating feature: it is intended to bring all themes up-to-date, so that they can format all the styles that users have not been seeing for years (for some, it’s a decade or more of missing syntax highlighting).
@Drift91: As with all styles, if you don’t like the formatting that is chosen by default for a given style, you are free to change it for yourself. You go to Settings > Style Configurator > Language:
INIor Language:Properties, select Style:KEYand change the Italic checkbox, as shown here for INI:
-
Bug report: Find in files causes Notepad++ to crash. Have upgraded to 8.9.1. No improvement. Windows version 11 Home 10.0.26200 Build 26200
-
@Pete-Davis said in Notepad++ v8.9.1 Release:
Bug report: Find in files causes Notepad++ to crash. Have upgraded to 8.9.1. No improvement. Windows version 11 Home 10.0.26200 Build 26200
Cannot reproduce. Find in Files works just fine with v8.9.1 for me. You will need to be more specific than that.
- ?-menu Debug Info
- Exact sequence of events that cause it to crash
- State of Find in Files dialog before the crash (what values, what options enabled, what buttons you pressed, etc)
-
@Pete-Davis, if you’re using WebEdit, a fixed version is already available.
