Notepad++ v7.4 released
I have made Edge as my default browser recently (nice browser BTW, a lack of “search in Google” command though), one of awesome features in Edge is peeking page while mouse hovering on a inactive tab.
Notepad++ has stolen this feature shamelessly - in the version 7.4 Document Peeker has been added. By hovering mouse on any inactive tab, you can preview document displaying under the tab, or / and on document map. This feature can be disabled easily by unchecking “Peek on tab” of Document Peeker, in MISC. section of Preferences dialog.
There are a lot more of enhancements and bug-fixes in this version. Please check in the change log of download page for more details.
Thanks for the new version Don.
Thanks, but can one disable the online connection on startup, it takes too long to open the document when the internet connection is blocked?
Went back to 7.3.3, no delay.
Why do you still have an old Plugin-Manager in the installer file? I get the 1.3.5, but when I update I get the 1.4.5. Couldn’t you include the actual version if you deploy new releases?
can one disable the online connection on startup
I cannot reproduce it after disabling WiFi connection on my laptop.
What kind of online connection are you talking about?
Could you provide the debug info (via menu ?->Debug Info…)
Thanks for the new version!
The item 9 (“Apply the new file custom encoding (Unicode or not) while opening an empty content file”) works great on Windows 7 x64 with the Notepad++ v7.4 x86 version.
Not him, but yes there is a connection on each startup that slows the program down with v7.4.
Never had this happen with previous version, my settings have not changed and everything “connection related” ie. auto-update, cloud, etc. are checked off.
Is this the right place to file a bug for v7.4 64-bit version? I ran into a problem:
1: I create a new empty file in explorer.
2: I open the file in np++ 7.4 and add some text.
3: If I then try to save the file I get either:
The File cannot be saved and it may be protected.
Do you want to launch Notepad++ in Administrator mode?”
Failed to save file.
Not enough space on disk to save tile?”
Running as admin does not make any difference.
I found the cause for the error: when encoding is set to UTF-8 in the new documents settings this error occur. If I choose ANSI or UTF-8 with BOM, saving works (I have not tried all other encodings).
This is on Windows 10 x64.
Notepad++ v7.4 (64-bit)
Build time : May 14 2017 - 21:02:35
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 10 (64-bit)
Plugins : mimeTools.dll NppConverter.dll
Which version of Windows do you use?
It could be the checking of certificate chain (the root + intermediate authority).
AFAIK, in a modern OS ( > Windows 7) the certificate chains are in the OS, however, they may not complete in the old OS, so WinTrust library check it online directely.
@Petter-Österlund I can reproce it - it’ll be fixed in v7.4.1
Thank you for the heads up.
Windows 10 Creators update, again though, going back to v7.3.3 does not do this, it’s only with version v7.4. So something changed with this version.
Seems I can’t edit my old post anymore, but I just wanted to let you know that I reinstalled v7.4 after going back to v7.3.3, and this connection does not happen anymore… I’m not sure what has changed. Weird either way.
@ImSpecial Please let me know if it happens again.
Bah I spoke too soon, it did go away for a bit… but it seems on a PC reboot, the first launch of NP++, that connection makes my firewall pop up again, until I just give it an allow rule. kind of annoying for me since I like to keep a very tight, small amount of rules for my firewall.
I hope this can be worked around.
@ImSpecial So can you reproduce this issue steadily?
It seems so, it also seems to be tied to Windows Cached Certification Files, if these get cleared for whatever reason, a connection prompts.
This issue has been fixed. Please try this binary (x64 version, to replace the original one):
and confirm me the issue is gone.
I tried this and it does seem fixed… we’ll see if this comes back later though. Thank you for fixing this BTW!
@ImSpecial You’re welcome. Feel free to let me know if this issue persists.