@sevem47 said: Just for your information; this is something I can NOT confirm. For me Search++ even runs on my old, not up to date Windows 7 machine (see below debug info). Perhaps this is as well a question of having all the “correct libraries” to be able to run the plugin. Well, that’s interesting. Thank you for that information! I will take a closer look.

@J-Mark-Barfield , that was not a “regedit”, that was a normal command-line command all those two commands did was run an instance of notepad++.exe without RunAsAdmin privileges, even before you made the change to the executable compatibility settings it was completely unnecessary all you had to do was exit Notepad++ application completely (so it wasn’t running), then do the steps I explained to get notepad++.exe to not run as admin, and then the next time you ran Notepad++ (either using your shortcut or double clicking on the exe or running the exe from the command line normally or double clicking on a text file or right clicking and choosing Edit with Notepad++) would have run Notepad++ not as admin if you didn’t exit Notepad++ first, then the still running Notepad++ instance would still be running as Admin. Changing the exe properties while the exe is running doesn’t magically drop the running Notepad++ out of Admin mode. And thus your right click would not have worked, because the running Notepad++ was still in Admin mode. all you did by doing those extra commands was close the Notepad++ that was running as admin open a new instance that wasn’t running as admin change the exe properties so that it wouldn’t run as admin next time (I understand that you got it working, so you don’t really care at this point. But I don’t want future people to read this discussion, and come to the wrong conclusion that they need to do your extra steps. Those steps were completely unnecessary.)

@PeterJones thanks mate.

@PeterJones Without the whale, it’s just Burns and Allen.

@Afik-Gilboa said: and I am not doing “run as admin”, at least not on purpose Your Debug Info clearly indicates you are running as Admin, and I believe that your Notepad++ title bar will also say Administrator on it. If you aren’t doing it on purpose, then you need to check your Windows right-click Properties on notepad++.exe and whatever shortcut you are using (on your desktop, task bar, or start menu) and see if one of them has it set to run as Admin in the Compatibility tab (see this recent discussion if you need more on how to check executables or shortcuts for run-as-admin and how to change that). there is no “NppFTP.xml” file in Documents. Ugh. I had forgotten this, because at one point I knew that NPPM_GETPLUGINSCONFIGDIR ignores cloud or settingsDir settings, and instead always uses either AppData or Portable. Annoying “feature” of the message. :-( Sorry for the bad memory. So, anyway, that means that NppFTP should be using %AppData%\Notepad++\plugins\config\NppFTP\ directory, and the NppFTP.xml should be there, instead. So that’s where you should go looking for it. See which of those directories exist, and look at the permissions of the directories and files there.

@Passant-Delarue , Initial guess: turn off “. matches newline”, otherwise your .* will greedily match the whole file.

Since it’s essentially working at this point, I’ve renamed the Topic to “BETA” @mpheath , I have updated the README at https://github.com/pryrt/NppPlugin-HiddenLexers to enumerate available options I think I’ll be patient, and give the beta test a while longer, so won’t try to rush to release it before N++ v8.9.8’s PluginsAdmin list is finalized.

@Krzysztof-Blachnicki said: I deleted ExtSettings.ini (which was 0 byte) and… It works again. Maybe it’s n++ fault, but… For other plugins settings aren’t gone and when files are 0b they don’t cause glitchy behaviour. I’d bet it’s rather a problem with this particular plugin. If deleting the ExtSettings.ini caused the problem to go away, then I am confident it is the plugin, not Notepad++ itself, that is the culprit. The question is what now? Whom I can ask for reaction? Report the problem to @dinkumoil , the author of the plugin => https://sourceforge.net/projects/extsettings/support

Search++ version 0.6.4 is available. It is expected to fix the bug reported here. Even though it seems most people never experience that bug, I still recommend upgrading at the next convenient time, so we will all be testing the same code. It’s always possible that I broke something else. I am still working on improving the multi-threading for find in files. I’m also trying to decide how best to mitigate a problem wherein Search++ fails to load when a particular Windows redistributable library has never been installed on the system. More updates should be coming before too much longer. All thoughts, suggestions, comments, criticisms, bug reports and raspberries are welcome, and thank you to everyone willing to give this jalopy a good work-out.