It looks like @LucaSorvillo took me up on the recommendation: Created new Issue #18496 , so there’s an “open issue” to PR against Created PR#18497 to implement it as a sub-option of the Tab Bar > Behavior > Vertical option

Hello, @coises and All, Many thanks, @coises, for your new release. Sorry for the late reply — every Friday, since the beginning of fall, I’ve been going on hikes with a group of seniors ! You said : Correct failure to find a zero-length match at the end of a file, selection or span of marked text when the previous match included last character of the file, selection or span of marked text. I did verify, for example, that the regexes ^(?-s)((?!test).)*\R|\z, (?-s)^((?!test).)*$\R? and (?-s)^((?!test).)*(\R|\z) correctly detect the last empty line 10. Nice ! You said : Condense Tools | Synchronize sub-menu. To this purpose, here is a little test, using my example text, below, pasted in a new tab : bla blah this is the test to do bla blah test bla blah Preamble : Uncheck, if necessary, the Bookmark lines when marking text (Shift: Configure) option in the Tools menu Uncheck, if necessary, the Default commands search within selections option in the Settings dialog Uncheck, if necessary, the Default commands search within marked text option in the Settings dialog Uncheck, if necessary, the Always unmark all text before Mark command. (Otherwise add to existing marked text). option in the Settings dialog Now : 1 Mark every test word 2 Mark every blah word 3 Then, manually, bookmark the lines 4 and 7 containing the word test 4 Choose the Synchronize marks and bookmarks option 5 Finally, hit the Shift key and click on the Mark all text in bookmarked lines (Shift:clear first) => All the existing marked test is cleared first, then all text, in the two bookmarked lines, is marked, as shown below : [image: 1792245552765-59f2b21f-6c1e-4681-a740-34a1bee6c7f8-image.jpeg] 6 Now, use the Remove marks from active document document to clear all the marked text and click on the two blue bookmarks to clear them, as well 7 Redo the steps from 1 to 4 8 Finally, simply click on the Mark all text in bookmarked lines (Shift:clear first) => All the existing marked text is preserved, then all text, in the two bookmarked lines, is marked, as shown below : [image: 1792245583295-64d10cec-acda-4f8b-870f-eba6af5b26d1-image.jpeg] You said : Implement Tools | Expand visible configure tool window. Bravo for your new configurable dialog via the Expand visible 1:1 (Shift:configure) option, in the Tools menu. Every click, possibly repeated, on buttons Expand before, Expand after and Expand act as expected ! [image: 1792245636740-56bcd802-4314-4681-93c2-dd8a24afcc25-image.jpeg] The button Reset clears all these context lines and I suppose that the save button ( not tested ) can remember special settings like : show me, by default 3 lines before and two lines after ! You said : Hidden lines now show unhide margin markers. Hidden lines stay hidden after leaving and returning to a tab (except for the first and last line,… As an example, I chose to hide all lines containing the the property string, with this exact case, in the ICU.txt file : I had the bottom message Showing 13 matches and, indeed, only 13 lines were visible. However : I did not see any unhide margin markers ??? While switching to another tab then switching back to the ICU.txt did show me all the property strings but all the lines were visible and not the 13 lines containing the the property string only ??? Best Regards, guy038 Oh… I have not read your very last post yet. You said : Show only lines with shown text, and the Reset button in the Expand visible dialog, do not restore hidden line markers correctly. Personally, I did not notice this bug, even when clicking on the Reset button during my test with the ICU.txt file, described above ?

@Troglo37 , It’s much too late now, but for “open all tabs”, Notepad++ has the session.xml.inCaseOfCorruption.bak, which should be one version of your session file out of date (for example, my session file is dated yesterday at 7:13pm, and my corruption-backup is from 2:37pm that same day). So, in the future, if you open Notepad++, and it doesn’t have all your old session files open, before doing anything (before closing Notepad++ or trying to save or load anything), make a copy of session.xml.inCaseOfCorruption.bak to tryme.session.xml so it won’t be overwritten, exit Notepad++, rename session.xml to bad-session.xml, copy tryme.session.xml to session.xml, and start Notepad++: that should take your in-case-of-corruption session as your active session … so if the previous time you exited and started was good, you should be back to that session. That won’t fix your corrupted stylers (colors). Unless you had a recent change in one off your Style Configurator settings, I am surprised Notepad++ was trying to write to your stylers.xml, because it only tries to write it if there was a change. But maybe the reboot process confused some bit in memory making Notepad++ think it needed to.

@shocked-gamer , @peterjones is right. I only use Firefox myselff, and it’s in dark mode right now…however, you have to be signed in. For instance, I always sign out. When I do, the light theme comes back on, until I again, sign in. I believe it’s linked into your account, and it apparently works, or it wouldn’t go dark after I’ve signed in.

@myfancytextgenerator , In your first few posts here, you didn’t post links, so despite your username, I hoped you were honestly here to talk about Notepad++. It appears I may be wrong. But just in case, I am giving you grace for your one mistake. This forum is not a place for getting the word out about your fancy text generator. Any more spam links from you, and you will be banned.

Years later, I finally had the time to figure out how to implement “UDL as Default Language” for PR#18499 to close my Issue #11097 and related Issues. It was just just merged, so will be in the upcoming v8.9.9 RC

Echoing what @Lycan-Thrope said — it is worth trying the GDI workaround before settling on the old Compare plugin, because that older plugin is no longer maintained and can develop incompatibilities with newer Notepad++ releases. To try the fix suggested earlier in this thread: go to Settings > Preferences > MISC., find the rendering-mode drop-down (DirectWrite is the default), switch it to GDI, then fully restart Notepad++ and run the same comparison again. The crash appears tied to how ComparePlus draws its difference highlighting under DirectWrite, so GDI sidesteps it. Two extra things worth checking if it still crashes: Test with all other plugins removed, in case something else interacts with it (XML Tools was installed alongside ComparePlus in the original report here). Check whether file size or shape matters — try a small pair of files first, then the large XML files, to see whether size plays a role. If you get a chance, please report back whether the GDI switch helped. The plugin author said a reworked ComparePlus is on the way that should fix the DirectWrite problem, so a data point either way helps everyone following this thread.