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

Yes, you can get bold/italic text directly into Notepad++. As Coises explained, those “bold” letters aren’t formatting at all; they’re ordinary Unicode characters from the Mathematical Alphanumeric Symbols block. Notepad++ is a plain-text editor, so it can’t do rich-text bold, but it handles these Unicode characters like any other text — you can type, paste, search and replace them. Two easy ways to insert them without a website: Edit > Character Panel, then double-click the characters you want. Type the character’s hex code point and press Alt+X to convert it (e.g. 1D44E for 𝑎). If you’d rather convert longer passages in one go, a fancy text generator turns plain text into dozens of stylish Unicode fonts — bold, italic, script and more — ready to copy into Notepad++ or Facebook. Just keep in mind what Coises said: they’re still plain characters underneath, so editing them afterwards means retyping or regenerating that part.

Search++ version 0.7.2 is available Additional known bugs thus far: Show only lines with shown text, and the Reset button in the Expand visible dialog, do not restore hidden line markers correctly. That’s a simple omission which will be fixed in the next release. Some Search++ operations that affect hidden lines do not take into account the possibility that the hidden and shown lines and the markers in the margin that indicate hidden lines can fall out of sync. If the same file is opened in both views, Search++ affects hidden/visible lines only in the view which is active, but the markers are changed in both views. In Scintilla, markers and fold points are properties of the document, but hidden lines and whether a given fold is expanded or contracted are properties of the view. Because Notepad++ uses markers to keep track of hidden lines and to implement the ability to show them again, there’s a bit of a conflict. In principle, it should be impossible to have lines shown in one view and not in the other, except when the only thing hiding lines is collapsed fold points. As far as I can tell, Notepad++ doesn’t let you hide or show lines in one view of the document without the same thing happening in the other view, so long as you use only native Notepad++ commands. However, it’s useful to be able to have one view showing the entire document and another showing only lines of interest, and I don’t want to break that. The extent of problems this might cause is not yet known. For now, expect surprises if you open the same document in both views and use any of the Search++ features that affect hidden lines.

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