@Claudia-Svenson said: I would have expected from such a feature-rich tool like NP++ That I can mark/select just a part of the full text and convert it in-place to a new encoding (by a new menu or via smart via described earlier). All that without switching back and forth encoding and using clipboard. Probably there is no such tool included because this is a situation that should very, very rarely happen. One file normally contains one encoding — that applies everywhere, not just in Notepad++. (I believe there are some legacy exceptions for East Asian languages, but in those cases the encodings themselves include bytes that describe the encoding changes. To the best of my knowledge, Scintilla, and therefore Notepad++, does not support them.) If this is happening to you often enough to be a concern, I urge you to look earlier in your process. How are you winding up with files which contain characters in more than one encoding? As you can see from this demonstration, copying text from one encoding and pasting it into a document with a different encoding ordinarily converts the text to the encoding into which you paste it. So just copying and pasting from some other source should not cause this problem. I am not ruling out that there could be a bug, whether in Notepad++ or in some other program, that is causing you to get wrongly-encoded text in a file. If so, we should identify that bug. (Especially if it turns out to be in Notepad++, where possibly it could be fixed.) It is also possible that there is a step in whatever procedures you are following that predictably causes this, like concatenating two files with some other tool without first making sure the files have the same encoding, or using Edit | Paste Special | Copy/Cut/Paste Binary Content inappropriately. If someone else is supplying you with files that contain multiple encodings and you can’t prevail upon them to correct their procedures, then using a Python script, as @mpheath suggested, is probably the best solution.

If I can suggest one small improvement: take a look at this GitHub issue and apply the changes recommended there, mutatis mutandis, of course. Very few developers are aware that plugin panels can be automatically restored by the Notepad++ Docking Manager (which still lacks a completely documented API, unfortunately), but there’s always at least one user who notices that it’s not working as expected.

@ReeceBonneyTT , Known issue. Already fixed in the v8.9.7 Release Candidate You can download and test from that post; if it doesn’t fix your problem, report it there.

@Sylvester-Bullitt , Release Candidate is available. You probably want to test this version, and report any continued problems with the Open File feature ASAP.

Search++ version 0.6 is available. The big change in this version is the addition of a Search in Files dialog: [image: 1783211949656-7beeed4c-7d6c-4c3e-8b34-84e9473c4215-image.jpeg] There have been a few small fixes elsewhere — by now I’ve forgotten what they were — but mostly this release is for Find in Files. Adding that led to quite a few changes in code it shares with the existing functions, so unfortunately there could be new bugs in old functions. On the whole, though, handling of the search results list should be improved for all functions that use it. If you don’t like to read help, at least don’t forget to try right-clicking the text entry boxes and items in the file list. Replace in Files is planned but not yet implemented.

@PeterJones Worked perfectly, thank you.

@Mario-Lemelin , everything work fine except for the equations in latex Not all Markdown processors understand LaTeX. (For example, the Markdown processor for this forum does not.) It appears that MarkdownViewer++ does not have that feature (which doesn’t surprise me). I visited this site (https://github.com/npp-plugins/plugintemplate) but was unablew to find help. That site is just the repository for the C++ template for creating a plugin. It’s not going to have information on how to use any specific plugin. The home for MarkdownViewer++ is https://github.com/nea/MarkdownViewerPlusPlus , so that’s where you’d have to go. But the author has recently set the repo to “read only”, indicating that they are unwilling to support that plugin any more. However, there are other Markdown plugins available from Plugins Admin. I’ve never used them, but two I see include NppMarkdownPanel @ https://github.com/mohzy83/NppMarkdownPanel AnotherMarkdown @ https://github.com/ezyuzin/NppAnotherMarkdown this appears to be a fork of NppMarkdownPanel with a different feature set. when I look at its README, it mentions the ability to use katex for math (I think it’s an option that you’d have to enable by editing a config file for the plugin; you’d want to experiment and read the documentation for that plugin to be sure) – and a quick look at the katex description implies to me that it’s essentially LaTeX compatible syntax. You can install either of those from the Plugins Admin interface. It may be that one of those will do what you need (my bet would be on the second as your best chance).

@blueicehaller , Plugin commands, like Plugins > MIME Tools > URL Encode cannot be recorded in a macro. However, we have a sub-FAQ: “Using Plugin, Run-menu and Macro Commands in Macros” which explains how you can manually edit a recorded macro to include such a command (noting that caveat that if you add or remove plugins, you might have to update your macro to refer to the new menuCmdID for the plugin command).

Thank you again for your help.

@Howard-Brown @peterjones has given you the necessary information to get back the default DarkMode settings, so you should learn from this issue and do what I did, and make your own DarkMode settings by copying that file, and giving it a different name. I called mine MyDarkModeDefault to avoid the confusion, and played with it to my hearts content. Doing this trick, even with your new default version, you can make another copy and continue to fine tune what you need to, without damaging the default, or your own new default versions. Call it MyExperimentalDarkMode, and have fun without worrying. As @peterjones and many of us around here always say, “back up what you don’t want to lose or recreate” - though that is paraphrasing. :-)

Thanks, your script works perfectly.

Hi, @dougk.az, @peterjones and All, Oh, yes, Peter, you’re perfectly right ! But I must be a little tired from this heat wave. Since June 22, in the room where my desk is, even with a fan, the temperature has usually been between 29 °C and 30.5 °C. It’s awful ! BR guy038 Oh ! Now, I also realized that @dougk.az never spoke about the form feed ( FF ) characters, of code \x0C but spoke about the line feed ( LF ) chars, of code \x0A As I said above : really tired by heat !!!

@vvPeterJones I switched Settings>Preferences>Print from “No background color” to “Black on white” and the print is much better.

Even if the shorter, similar string was after the longer string, the same Regular Expression (Regex) can be used to get the same result:- Input abcdefghijklmnopqrstuvwx abc Output abcdefghijklmnopqrstuvwx ABC Explanation: The abc.*xyz preceding the (SKIP)(*F) in the Regex helps skip the long string starting with abc and ending with xyz and matches the other abc in the shorter, similar string! By using that Regex (mentioned in my previous post, just above this), the abc after the (SKIP)(*F) is matched, found and replaced.

@PeterJones Great. Thanks

Hello, Trying to do IPv6 in Syntax Highlighting for FortiOS. As I wanted to have a different font color for the dots and the colons in the IP address, I use those as operators, and have 0-9 A-F (Uppercase A-F) as keywords set to prefix. This only works if you’re building configs though, and will go back to default if there are lower case a-f hex values if you do a copy/paste type of thing in NPP. I chose to opt for uppercase A-F since all FortiOS words are case sensitive and must be lowercase(Not strings/objects mind you). You can, while configuring the device, set IPv6 addresses with these uppercase hex values. Note: You can specify objects without string delimiters, but I find that to be bad form. And if you include grep filtering in NPP, these keywords could be exposed. Keywords List Group Prefix Mode: Checked 0 1 2 3 4 5 6 7 8 9 A B C D E F Operators 1 . : /

I requested here: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/17508 I then made a plugin here: https://github.com/shoulders/npp-exclusive-file-lock Thanks