Thank You Everyone for your Time and Effort.

I said, will save two copies of the file whenever a save is triggered – it will write the main file, and it will write to the defined backup location: So, that’s technically true, but I had forgotten a small caveat, that came as I was verifying my assertions in a portable Notepad++ with AutoSave turned on to save every 1 minute: What happens is that when a save is triggered (either from the save button, File > Save, or the AutoSave plugin), Notepad++ copies the current contents of the file on disk to the backup location, then saves the new edits to the original location – so the backup is always one version out of date w/r/t the main file. If that’s really what you want, then my description still holds – it solves 2/3 of the problem. If that’s not right, and you really want two identical copies of the file saved, it would have to be a custom solution, because saving two identical copies in two locations, every time a file is saved is not a normal feature of a text editor. However, that could, theoretically be implemented by making a custom plugin, or (easier) through hooking into either the FILEBEFORESAVE or FILESAVED event using one of the N++ scripting plugins, like PythonScript or LuaScript.

@smcclosr said: Not 100% user if this version addressed this specific issue, It almost definitely did not. The changes between 8.9.6 and 8.9.6.1, as announced in the forum and by looking at the git-diff at GitHub, were completely related to vulnerability fixes (COPYDATASTRUCT, removing commandLineInterpreter hidden config file option, and making it harder for saved-Run-menu entries from shortcuts.xml to run apps from non-approved directories), and do not seem in any way related to OneDrive. (And least, I don’t see how any of them could affect saving of files to OneDrive) My guess was the change in v8.9.6 that changed behavior relative to v8.9.5 was the “saving dirty read-only files” fix (but that’s just a guess… and it wasn’t changed/reverted in v8.9.6.1, so that doesn’t seem a plausible explanation for your experience.) but it is resolved for me now. Hopefully it stays that way. Good luck.

@PeterJones Which debugger did you use? The problem with all of them is—to quote the DAP specification Since launching is debugger/runtime specific, the arguments for this request are not part of this specification. figuring out how to start them. I do hope that they all have one thing in common: that they expect this as a valid JSON message, which I define as launch_args. I tried it using the link from @rdipardo, but unfortunately it didn’t work properly. I was able to run through my simple test code step by step, but the variables weren’t returned. That might be due to my configuration or setup, though. @lycan-thrope Yes, as long as the debugger supports dap there is a chance that it will work with this client. Note that all dialog boxes are Scintilla controls and are not protected by the “Read-only” setting. However, this should not be a problem, with the exception of the Breakpoint View, where the client receives information about which breakpoints are currently set. The markers in the source code—currently only in the active document—are removed after the debugging session stops, but they remain in the breakpoint view so they can be reused in a later debugging session. The exception, of course, is if I click on an already set breakpoint again; then it is also deleted, and of course if I select and delete something in the breakpoint view… Just for reference the config I used for the linked perl-dap [perl] debugger = "C:/WHATEVER_DIR/perl-dap.exe" debugger_args = ["--stdio"] mode = "io" # debugger_args = ["--socket", "--port", "13603"] # mode = "tcp" # host = "127.0.0.1" # port = 13603 env = { PATH="C:/compilers/strawberry-perl-5.42.2.1/perl/bin", } launch_args = '''{ "program": "C:/repos/nppdebugger/tests/debuggees/perl/test.pl", "cwd": "C:/repos/nppdebugger/tests/debuggees/perl", "perlPath": "C:/compilers/strawberry-perl-5.42.2.1/perl/bin" }'''

This issue is one of the most consistently duplicated on the forum, for example: “Highlight HTML and CSS” “CSS comments should be in GREEN” “css formatting not working on embed style sheet…” etc. @peterjones’s initial reply is the correct one. You can also refer to this more detailed explanation regarding the current limitations of Lexilla. For now, a relatively simple way to edit HTML documents with embedded style and script highlighting is to use the tree-sitter plugin. Note that only “light” style themes are currently supported, and you will have to manually download and extract the configuration files to get it working. [image: 1779564282293-npptreesitter-v110.png]

GitHub repository: https://github.com/hassaine-abdellah/npp-language-selector PS: I commented the code well so the curious developer can understand how it works.

@peterjones Yes, mostly the issue is for end user. Thanks for complete explanation!

@CJBlake1 , Rereading my original response, that came out harsher than I intended. I got interrupted with real life, and had decided to post as-is, before I had a chance to audit my post, so it was too “raw”. What I was really trying to say: I don’t think the specific version of Edge is really relevant to your issue. I am assuming that you used to have XML associated with Notepad++, and then suddenly it wasn’t anymore. Unfortunately, many applications (Edge included) have programmers who think that there software is the only one that matters, and that they should “take back” their favorite filetypes (like XML), regardless of decisions a user has already made. So I’m assuming that some recent update in either Edge itself, or in Windows in general, caused Windows to change (or reset) the default application for the XML filetype. There is nothing that Notepad++ can do to prevent the OS or an overeager application from hijacking the filetype. The best thing you can do in a situation like this is to use the OS tools to re-associate the filetype with the program you want. In Windows 11, the most reliable method for doing that seems to be using the Open With from the right-click menu: right click on an XML file, choose Open With, select Notepad++, and be sure to say, “always use this app from now on”.

@guy038 said: First, regarding the bug I mentioned in my two previous posts, I also detect it with native N++ and, for example, the Find Results panel : Thank you for that additional information. I had a suspicion this was a Notepad++ behavior not really related to the plugin. I have not been able to reproduce it. It is possible that it is dependent on some detail of your operating system or drivers. Since you can reproduce it without any plugin, I suggest adding it as a Notepad++ issue if you think it is worth further investigation. It could be that others will be able to reproduce it, perhaps including someone who can run Notepad++ under debug and close in on what is going wrong.

Hi, All, Second and last post regarding the Word_Frequency macro ! Now, a simple example : Open the change.log file of the last release v8.9.6 Do a stream selection of all the points of the v8.9.6 release, ONLY. So, the lines below : 1. Fix vulnerability (CVE-2026-46710) of v8.9.4 & v8.9.5 installer. 2. Fix x86 installer regression of not showing installation entry in Control Panel's "Unstall a program". 3. Fix x86 installer regression where context menu not installed or uninstalled correctly. 4. Fix UAC prompt display regression (“Notepad++ installer” instead of “Notepad++”) for Notepad++ v8.9.5. 5. Fix incorrect bevaviour when saving dirty read-only files. 6. Fix regression where saving a UDL file removed XML declaration. Run the Word_Frequency macro. You should get, at once, this OUTPUY text : 1 : 1 2 : 1 3 : 1 4 : 2 5 : 3 6 : 1 9 : 3 CVE-2026-46710 : 1 Control : 1 Fix : 6 Notepad : 3 Panel's : 1 UAC : 1 UDL : 1 Unstall : 1 XML : 1 a : 2 bevaviour : 1 context : 1 correctly : 1 declaration : 1 dirty : 1 display : 1 entry : 1 file : 1 files : 1 for : 1 in : 1 incorrect : 1 installation : 1 installed : 1 installer : 4 instead : 1 menu : 1 not : 2 of : 3 or : 1 program : 1 prompt : 1 read-only : 1 regression : 4 removed : 1 saving : 2 showing : 1 uninstalled : 1 v8 : 3 vulnerability : 1 when : 1 where : 2 x86 : 2 If you prefer a ordered list ignoring the case, simply insert the regex replacement, below <Action type="3" message="1700" wParam="0" lParam="0" sParam="" /> <Action type="3" message="1601" wParam="0" lParam="0" sParam="(?x-i) \u+" /> <Action type="3" message="1625" wParam="0" lParam="2" sParam="" /> <Action type="3" message="1602" wParam="0" lParam="0" sParam="\L$0" /> <Action type="3" message="1702" wParam="0" lParam="640" sParam="" /> <Action type="3" message="1701" wParam="0" lParam="1609" sParam="" /> Right before the sort line : <Action type="2" message="0" wParam="42059" lParam="0" sParam="" /> Here is the trick to get the right number of occurrences when > 99,999. Search for any remaining ¶ character with the regex ¶+ . Let’s suppose you have this line : the : ¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶¶97371 As the number of consecutive ¶ is 23, the exact of occurrences of the word the is : 23 × 10000 + 97,371 i.e. 327,371 occurrences Remember that the first thing to do, before running the Word_Frequency macro, is to select part or all current file contents ! Best Regards, guy038

@Italian-menu , Why in the world would you think your post helpful? “depending on what you’re using” – of course they are using Notepad++. This is a Notepad++ forum. If you cannot give a human-created Notepad++ -specific answer, don’t bother posting.

@donho , https://community.notepad-plus-plus.org/topic/27545/inability-to-save-file-to-onedrive-with-8.9.6-version-of-notepad indicates that there might be a regression with the ability to save to OneDrive…

@PeterJones Thanks!