Link you’ve posted expects VS2015. I have lots of errors. Beginning with “using static” od Kgb namespaces.

@dragonmenorka Check the correct directory structure of the installed plugin “Python Script”:
https://notepad-plus-plus.org/community/topic/17777/python-script-support-in-versions-of-npp-7-9-2/2
https://notepad-plus-plus.org/community/topic/17256/guide-how-to-install-the-pythonscript-plugin-on-notepad-7-6-3-7-6-4-and-above

@PeterJones Okay thank you.

welcome to the notepad++ community, @Richard-Linhart

i can’t yet reproduce that opening a .cfm file, causes an abnormal notepad++ shutdown.

please test the following, to verify, if a clean notepad++ (without any 7.7 incompatible plugins that could cause this) would be able to open them on your system.

download the notepad++ 7.7 portable version from >>> here <<<.
(the portable version does not require any installation and runs completely independent and isolated from your installed version. all custom settings, as well as any stuff you might want to try at the portable version, will not modify your installed version)

extract npp.7.7.bin.zip to your desktop.

important note: make sure to close all instances of notepad++ that might be running, before starting the portable version at the next step, to make sure you are using this portable version.

open the extracted npp.7.7.bin folder and start this portable version by double-clicking on notepad++.exe inside this folder.
(note: notepad++.exe will just be seen as notepad++, if you have enabled to hide all known file extensions at your explorer settings)

try to go to the menu file > open and open any .cfm file and report back what happens.

many thanks and best regards.

@dail said:

The Scintilla developers are not at fault. This is the entire reason they changed from the 3.x to 4.x version.

It is very much in dispute whether a library should ever allow itself a major compatibility breaking change to its API. Changing the library’s major version does not magically justifies it. This is definitely the Linux mindset with its advantages and shortcomings.
A responsible developer should go through all possible hoops to extend the API rather than change it before going this path. Maybe they did, I don’t know.

Specifically for this change, I would challenge, the need to support 64 bit position within a document. Opening a text file over 1GB is such a bad user experience that I doubt that you can find 0.01% within your user base that do it routinely. Your guess is good as mine for the amount of users that will be pissed by the compatibility break.

Still need to audit plugins to see how many are actually broken. Maybe I am overly pessimistic.
But it is possible that 32 bit version of Notepad++ just became much more attractive.

@rainman74

thanks.
note: hexeditor x86 and x64 binary builds are already available at @chcg 's repo:
https://github.com/chcg/NPP_HexEdit/releases

greetings.