Notepad++ 7 - 64-bit Available
-
@Sean-McPoland
@Mohammad-MasoumiThe plugin manager has been left out of the 64-bit version of Notepad++ because a 64-bit version of the plugin manager does not exist. And you are correct that very few 64-bit plugins currently exist.
-
I found an interesting issue. When the “Commonad Argument Help” window is kept open，press Ctrl+S in the editor window will insert a special character, which is shown as a black background, white foreground block with the label ‘DC3’.
-
Lazy question before I try it: Does Notepad++ 64 bit support larger file size than Notepad++ 32 bit?
I have been using Notepad++ to convert large files of UTF-8 text data to UCS-2; they start around 450,000,000 bytes size and end up about 900,000,000 bytes. (There are other ways to do that, which I don’t have access to in my test environment, e.g. PowerShell 5.0 has capabilities.)
Notepad++ saves the larger file but then cannot open it - I assume this is not a flaw in my environment. I would like to be able to open the file and save it back to UTF-8. This should be identical to the original file, but that is what I want to test.
-
-
Without plugings for x64, it’s a pity…
-
come on, it’s brand new - plugins need to be developed/recompiled etc…
and even without any plugins, npp is still a fast and powerful editor.Cheers
Claudia -
The Windows 10 association function setting is invalid.
-
@Robert-Carnegie
Notepad++ (or the Scintilla component?) seems to use significantly more memory when styling is activated for the document. And it is much slower. Deactivate text styling before opening huge files or rename the file extension to an unassociated file extension, like *.xyz -
I’ll just add a me too to this one.
If you install NP 64-bit over the top of NP 32-bit then you can’t uninstall both.
Uninstall either 32-bit or 64-bit and both references are removed from ‘programs and Features’
there is also no way of telling of distinguishing between 32 and 64 bit versions in Programs and Features.This was on Windows 10 Version 1607, but I suspect that ain’t going to make too much difference.
thanks in any case for the port to 64-bit.
-
I stay in 6.9.2 are equal. Macro recording does not work
-
@dail said:
I’ve seen some uninstallers ask the user whether they’d like to keep their configuration files. Not sure how easy this would be.
I’m doing this feature. it’ll keep config.xml, stylers.xml, langs.xml, contextMenu.xml and themes files (all the files in
%APPDATA%\notepad++).
A message box with Yes and No buttons will be launched during the uninstallation. for asking users if they want to keep their user data.
Any suggestion about the message in this box? -
@donho I’m glad to hear it :)
Any suggestion about the message in this box?
I think a simple message would suffice, something along the lines of: “Would you like to keep your custom settings?”
-
Hi,
The bug is still there in version 7.1.
:)
This is working and the installtion will be i the folder C:\Pub
npp.7.1.Installer.exe /S /D=C:\Pub
:):(
The x64 version of 7.1 is not working.
The installtionfolder will be C:\Program Files\Notepad++
npp.7.1.Installer.x64.exe /S /D=C:\Pub
:(
When will you fix this bug???//Rickard
-
@Dave Tabz would like to when the 64bit pugin manager version will be ready
-
Perhaps add some info about why to use 64-bit version.
Why should users choose the 64-bit version instead of the 32-bit version and vice versa. -
@donho FYI, I just installed Notepad++ 7.3.2 64-bit version where there had been Notepad++ 7.3.2 32-bit version and it warned me about removing the 32-bit version while noting it would preserve settings.
I have done this several times since my original post - thanks for the changes to accommodate this.
However in this case I then ended up using the View Source command in Internet Explorer and got this error:
[Window Title]
C:\Program Files (x86)\Notepad++\nppIExplorerShell.exe[Content]
Windows cannot find ‘C:\Program Files (x86)\Notepad++\nppIExplorerShell.exe’. Make sure you typed the name correctly, and then try again.[OK]
Turns out the 32-bit installer had set this value at some point in the past in the registry and it was not modified or removed when I ran the 64-bit installer:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\View Source Editor\Editor Name
(Default) = C:\Program Files (x86)\Notepad++\nppIExplorerShell.exeSince the 32-bit program is removed, there is no C:\Program Files (x86)\Notepad++\nppIExplorerShell.exe
Further there is no 64-bit version of nppIExplorerShell.exe in C:\Program Files\Notepad++
You can, of course, replace the default value with “C:\Program Files\Notepad++\notepad++.exe” and IE will launch npp as the viewer although it will likely throw a security warning.
-
I literally only just found out Notepad++ has a 64-bit build. Sadly I switched to Sublime Text back in 2015 when I really needed a 64-bit editor to handle the monster text files generated by FEA software (Abaqus and HyperMesh, specifically) that Notepad++ choked on. Sublime has Linux builds also and a native, default dark theme, sooo gonna stick with that. Bittersweet though, because Notepad++ was one of my favorite apps right up to the point it couldn’t do what I needed it to :(
-
Depending upon the magnitude of the large filesizes you are talking about, your move may have been a good one (Notepad++, even 64-bit, is limited in the size of file it can open).
-
Updater was drawing a blank on my existing 64 bit install. I noticed it was quite old so I uninstalled so that I could install the latest version.
On the download page, when I click on the 64bit installer, I get an error message:
Error 503 Backend fetch failed
Backend fetch failedGuru Meditation:
XID: 180289907Varnish cache server
-
This post is deleted!
