Notepad++ v8.5.3 Release
-
@PeterJones The Link I see (http://download.notepad-plus-plus.org/repository/MISC/nppShell.TEST20/) doesn’t load. Is this the link you were referring to?
-
@usmcguy said in Notepad++ v8.5.3 Release:
@PeterJones The Link I see (http://download.notepad-plus-plus.org/repository/MISC/nppShell.TEST20/) doesn’t load. Is this the link you were referring to?
No. I was referring to the link https://github.com/notepad-plus-plus/nppShell/issues/29 , which was the link I embedded in my most recent post.
-
@usmcguy
Just checking if you are running get-appxpackage | remove-appxpackage before running sysprep? I build monthly updates of Windows 10 and 11 and run above command before I run sysprep to create them; did not have an issue with last month’s build that had 8.5.2. -
@Pete-Gomersall I did end up using the cmdlet to remove the AppX package before Sysprep.
-
@Jerald-Belleza I noticed this as well (I don’t recall what my previous version I had prior to the upgraded to the v8.5.3 version, but I always keep it updated so it must have been fine in the prior version).
My instance settings are set to “Always multi-instance mode”, but in earlier versions, when selecting multiple files in file explorer and “Edit with Notepad++” context menu option, it would place it in the same new instance not 1 instance per file! I learned this the hard way when I had over 2-dozen files selected! This is quite annoying now because I rely on that functionality and don’t want to have my instance setting to the default “mono instance”.
My OS is Win10 Pro, 22H2 19045.3031
-
If anyone else is mildly (or severely!) dissatisfied with the fact that non-printing characters and control characters no longer show up by default, here is an issue that I introduced
and here is the script that I created to show non-printing and control characters but notCRandLF:from Npp import * notepad.menuCommand(44130) # toggle all non-printing characters notepad.menuCommand(44131) # toggle all control characters (e.g., BEL, ENQ) -
@Mark-Olson said in Notepad++ v8.5.3 Release:
non-printing characters and control characters no longer show up by default
I haven’t looked at your issue, but defaults for these settings in 8.5.3 are:
- Show Non-Printing Characters (checkmarked)
- Show Control Characters & Unicode EOL (checkmarked)
-
There’s something that I don’t like regarding the new behaviour of the
Show Symbolfeature !
To explain my annoyance, follow these simple steps :
-
First, ensure that NO line is checked when selecting the
View > Show Symbolmenu -
In a new
UTF-8tab, add the following line, which ends with a line-break
abc def ghi jklmno pqrThis line contains the string abc, then four
Spacechars, the string def, aTabchar, the string ghi, theNarrow Non Breaking Spacechar, the string jkl, theETXchar, the string mno, theLSchar, the string pqr and ends with the usual\r\nline-breakNote that, as no
Show Symboloption is set, at this time, the3chars between the strings jkl, mno and pqr cannot be seen in N++ and theSpacesandTabsare only visible asblankchars ( Logical )
Now, successively, click on :
- The
View > Show Symbol > Show Space and Taboption
=> The
Spacecharacters between abc and def, as well as thetabcharacter between def and ghi should be seen- The
View > Show Symbol > Show End of Lineoption
=> The
\r\n( or\n) characters should be seen- The
View > Show Symbol > Show Non-Printing Charactersoption
=> The
Narrow Non Breaking Spacecharacter should be seen- The
View > Show Symbol > Show Control Characters & Unicode EOLoption
=> The two characters
ETXandLSshould be seenSo far, everything seems logical !
However, you’ll note that the
Show All Charactersoption was automatically checked, when we previously check theShow Control Characters & Unicode EOLoption
Now, click a first time on the
¶button ( standing for theShow All Charactersoption ) of the Tools bar => No visible change as all the options of theShow Symbolmenu are checked ( Normal )Then, click a second time on the
¶button => At once, all the symbols disappeared ! Of course, it has always been the behaviour of this option. However, regarding all the new options added to theShow Symbolmenu, I was expecting that :-
The
View > Show Symbol > Show Space and Taboption would be still checked -
The
View > Show Symbol > Show Non-Printing Charactersoption would be still checked -
The
View > Show Symbol > Show Control Characters & Unicode EOLoption would be sill checked
Presently, after this second click on the
¶button, we, unfortunately, have to redo all the process to be able to see most of these special characters, again !
What is your feelings regarding my proposition ? So, in other words :
-
The
¶button would check theShow All Charactersoption, if presently not checked -
The
¶button would uncheck theShow End of Lineoption only, if presently checked
Best Regards,
guy038
-
-
@guy038 It seems I commented nearly the same here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/13734#issuecomment-1575470110
-
I had the problem that the XML parsers from Microsoft ignoring CRLF in Text and always returning only LF. I don’t know if that’s in the spec but this is what happens if you read the XML.
So you will never get the real CRLF until you encode it somehow or use CDATA sections. -
@Tragen said in Notepad++ v8.5.3 Release:
I had the problem that the XML parsers from Microsoft ignoring CRLF in Text and always returning only LF. I don’t know if that’s in the spec but this is what happens if you read the XML.
So you will never get the real CRLF until you encode it somehow or use CDATA sections.And the workaround that works for v8.5.3 is in the FAQ
-
I think you should create a version for MacOS as users like me also would benefit from the use of this app. Hopefully this is added in the next update.
-
@Ahmed-Hakim said in Notepad++ v8.5.3 Release:
Hopefully this is added in the next update
Very unlikely to happen for any future version. Notepad++ is built on libraries that only work in the Windows environment.
There have been a few posts asking for a Mac version but thus far there has been no reference for any future release on the Mac.
See also this post.
Terry
-
This Version doesn’t work on Windows Server 2008:
Error:

Is it possible to fix this?
I revert to 7.9.5.
Witch Version is the latest for Server 2008?Please add in the download section always a compatibility list for the OS.
PS:
And the Plugin: compareplus does also not work on Server2008. -
@volker001 said in Notepad++ v8.5.3 Release:
Witch Version is the latest for Server 2008?
https://github.com/notepad-plus-plus/notepad-plus-plus/blob/master/SUPPORTED_SYSTEM.md
-
@donho sorry couldn’t remember the version prior. But looks like the issue is with OS as I am getting the expected result on Windows Server 2012 using the same N++ version.
This is what I expected with Multi-Instance enabled. Select multiple files, right click and Edit with Notepad++, files will then be opened in a single instance of Notepad++. Select another batch of multiple files, right click and Edit with Notepad++, files will then be opened in another instance of Notepad++.
-
@Jerald-Belleza said in Notepad++ v8.5.3 Release:
@donho sorry couldn’t remember the version prior. But looks like the issue is with OS as I am getting the expected result on Windows Server 2012 using the same N++ version.
This is what I expected with Multi-Instance enabled. Select multiple files, right click and Edit with Notepad++, files will then be opened in a single instance of Notepad++. Select another batch of multiple files, right click and Edit with Notepad++, files will then be opened in another instance of Notepad++.
Could you create an issue here:
https://github.com/notepad-plus-plus/notepad-plus-plus/issuesI’ll work on it if the issue can be reproducible.
-
@donho Done! Many thanks for looking into this!
-
@donho
I too have the same problem - it was in the previous version - I updated to the next (this one) hoping it had been fixed, but no. Certainly cramps the way I use NP now. -
@Howard-Grimmer
Having said that, I’ve just rechecked setting Multi-Instance mode - it now looks like it’s working fine - so perhaps has been a Win11 problem? Great, I can work freely again!