@Terry-R ,

And to you and yours and all the NPP people.

My humble abode.
HouseInLights2.png

I just wanted to come back and thank everyone again for their help. As I had hoped, I took parts of multiple suggestions and came up with a sequence of search-and-replace steps which has reduced my log editing time to under ten minutes for a full week’s worth. Two months into the new process and not a single glitch!

Best of all, I increased my knowledge base in the process. I love it when solving a problem results in my learning something new!

Again, thank you all for your help.

Hi @Alan-Kilborn ok thank you, I have just created the issue https://github.com/notepad-plus-plus/npp-usermanual/issues/457

@Arthur-Alunts ,

The font you set in Notepad++ is just how the text is displayed in the entire Notepad++ application – and every text file you open. Font information is not saved inside text files. If having multiple fonts in your document is important to you, then you need to look for a “word processor”, not a text editor. Notepad++ is a text editor, not a word processor. (Word processors include the bundled-with-Windows MS Wordpad, or MS Office’s Word, or free ones like LibreOffice. But word processors are not the subject of this forum, so that’s as much as you’ll get about word processors here.)

@PeterJones

Sorry for my late response, but I visit the forum only occasionally.

It seems like you felt my last comment was in some kind offending, rude or at least harsh. If this is true I beg you pardon, it was not my intention to be like that. Maybe it seems so because English is not my mother tongue and I was not able to find an appropriate wording when I quickly fired off my comment.

And of course no one can know every single detail of all plugins, even if they use them themselves.

The marker ID used for bookmarks changed in Notepad++ 8.4.6 (and later). It is now 20, instead of 24. So, all references to 24 in this thread and/or its script(s), should be changed to 20.

The marker ID used for bookmarks changed in Notepad++ 8.4.6 (and later). It is now 20, instead of 24. So, all references to 24 in this thread and/or its script(s), should be changed to 20.

The marker ID used for bookmarks changed in Notepad++ 8.4.6 (and later). It is now 20, instead of 24. So, all references to 24 in this thread and/or its script(s), should be changed to 20.

The marker ID used for bookmarks changed in Notepad++ 8.4.6 (and later). It is now 20, instead of 24. So, all references to 24 in this thread and/or its script(s), should be changed to 20.

@Alan-Kilborn No problems, I am just grateful that you guys were there to improve my understanding of NotePad and it’s configuration.

@Maxima-120

Your N++ debug info? (paste here info from the N++ menu ? -> Debug Info…)

Was there a Windows restart/shutdown involved? I mean - you (or Windows OS itself) restarted your PC while N++ was still running and then you have lost your N++ tabs after reopening the N++?

There’s a possible solution for this thread’s topic, HERE.

@Juan ,

See the FAQ

@PeterJones I corrected it, one less error in WP!

@Soyar-Tom

See here and here.

@PeterJones
Thank a lot , it works now. So i’d better to backup an offline manual to reference api . Thank everyone .

@Richard-J-Otter said in Font Linking to display glyphs not in font:

@astewart77 My understanding was that those registry settings were deprecated in later Windows versions. But the whole area seems badly documented in MS literature.

Here is a fresher link, dated Nov 2022, to a MS doc page for font fallback / fontlink. No mention of deprecation.

I have seen instructions on Google successful in Windows 10. On the other hand, this github bug report for Notepad++ says it stopped working after a Windows 11 release, for certain conditions. Apparently, it was still working in Windows 11 prior to that.

Using something that’s deprecated doesn’t make you a bad person. If your registry has font linking enabled, there will already be some entries there. No harm in adding an entry.

@rdipardo

I think your guess as to the OP’s data may have hit the nail squarely on the head.

It would have been abundantly clear earlier if the OP had posted a screenshot of what he was working with.

@Daryl-Vine

See HERE for more information on this topic.

To QUOTE the developers, “Already fixed, will be in the next N++ version” (presumably meaning 8.4.8).