Notepad++ 7 - 64-bit Available



  • Hi Don, I solved my problem. This is the solution:

    The program that you’re pointing to isn’t registered correctly.

    In regedit: Navigate to Computer\HKEY_CLASSES_ROOT\Applications and find your .exe name.
    Navigate under its name to shell>open>command. In the Default change its location to the actual location of the executable, hit okay and then try and reassociate the file type as you normally would.



  • @Eric-Winn
    You are pointing out an issue where there may be some incoherence.

    Indeed there are 2 scenarios :
    if user download installer for 64-bit and install it without remove old 32-bit one, both 32-bit and 64-bit binaries will stay in C:\Program Files (x86)\ and C:\Program Files\ respectively.

    OTOH, if user uninstalls 32-bit version before installing 64-bit version, all the settings will be gone. But user is aware of what they do so it’s a normal behaviour to me.

    I have no yet idea to solve this issue. If anyone in here has a thought, please let me know.



  • @donho

    I’ve seen some uninstallers ask the user whether they’d like to keep their configuration files. Not sure how easy this would be.



  • @dail How about remove automatically the 32-bit version while installing 64-bit version and vice versa?



  • I’m curious how other applications work that have both 32bit and 64bit installations.

    How about remove automatically the 32-bit version while installing 64-bit version and vice versa?

    That might be a good solution (possibly ask/warn the user?). Either way, I think a couple of things have to be considered:

    1. If 32bit and 64bit are allowed to be installed simultaneously:
    • Users might get confused. Using the windows shell to edit a file with Notepad++ might not always use the one they want.
    • At least all the config files should be compatible between 32bit and 64bit which is good.
    • Plugins will be different between the two. Also, if plugins are allowed to be loaded from %APPDATA% do 32 and 64bit try to load the same plugins? This could be a problem.
    1. If only one of either 32bit or 64bit is allowed to be install:
    • I’m sure someone will complain, but you can’t please all users :)
    • I’ve found it useful so that I can test 32bit and 64bit plugins…but there are several other ways to do this so not a big deal.


  • Macro recording, hang the whole





  • Crashes when recording a macro. Usually when you type a \ for a special character.

    I’ve reverted to 6.9.2





  • No PlugIn Manager?

    I assume it’s been left out until PlugIns are available…but shouldn’t it just list those available for 64 bit…meaning it should be there.

    Many thanks by the way,



  • @dail Good point!
    What’s your suggestion then?



  • @donho Under normal circumstances I don’t think users will need both. However, forcing a user to use just one might not be a good idea since there may be good reason to have both installed.

    So this is my suggestion (feel free to use it, or do something completely different :))

    • During installation (e.g. of 64bit Notepad++ version)
      • Check to see if 32bit version is currently installed.
      • If so, warn the user that installing both may cause problems.
      • Ask the user if they want to uninstall the 32bit version.
      • During uninstall of 32bit version, give the user the option to keep their current settings. This would probably be easy if they are using %APPDATA% but if they are using a local conf mode then the xml files won’t be in the right place, they would be under C:\Program Files (x86)\...

    Again this is just my suggestion so feel free to do whatever you feel is appropriate, and others may have better ideas. I am not familiar with NSIS so I don’t know the details of how hard or easy all this would be.



  • @Salimsg-Ibrahim i just wanted to point out the same solution, i found it on myself

    In regedit: Navigate to Computer\HKEY_CLASSES_ROOT\Applications\notepad++ and find your .exe name.
    Navigate under its name to shell>open>command. In the Default change its location to the actual location of the executable, hit okay and then try and reassociate the file type as you normally would.

    @donho i fear there will be a lot of users experiencing this problem, maybe you should try to get a fix before the automatic update causes a lot of troubles

    i like @dail solution

    @dail said:

    • During installation (e.g. of 64bit Notepad++ version)
      • Check to see if 32bit version is currently installed.
      • If so, warn the user that installing both may cause problems.
      • Ask the user if they want to uninstall the 32bit version.
      • During uninstall of 32bit version, give the user the option to keep their current settings. This would probably be easy if they are using %APPDATA% but if they are using a local conf mode then the xml files won’t be in the right place, they would be under C:\Program Files (x86)\...


  • More ported plugins:
    TagLEET
    lexamples



  • @Sean-McPoland
    Same issue



  • @Sean-McPoland
    @Mohammad-Masoumi

    The 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.



  • @Robert-Carnegie

    in theory yes, but at the end it depends how many ram can be used.

    Cheers
    Claudia



  • Without plugings for x64, it’s a pity…


Log in to reply