@dcog989 Thanks for this - if you have any tweaks or updates you’ve made since this comment, let me know!

@SMD40470 , I think the most likely reason (whether or not you think it’s “serious” enough) is that no one has asked for that feature, and the developer didn’t think of it himself yet. If it was just a UDL issue, I would probably say, “You should put in the feature request, but unfortunately, there have been no new features in UDL for over a decade, with a lot of really good feature requests that would be more fundamental to making UDL work better, so it’s doubtful it would be implemented any time soon.” However, based on this Issue about NFO files and OEM-US/CP437 encoding, it looks like there might be other people interested, even in non-UDL circumstances. So I wonder if the better feature request might be the more generic request, something like [FEATURE REQUEST] Allow setting preferred encoding on a per-language basis. However, there does currently exist a workaround: the AutoCodepage plugin can be used to set default encoding on a per-extension basis. While it might be nice to have it built in, the plugin currently provides the feature. Steps to get it to work: Have a UDL. In my example, I call it MyUDL and I give it the Ext.: smd, so all files ending in .smd will be treated as that UDL. (I picked smd from the letters in your username) Install the plugin Plugins > AutoCodepage > Settings Set Group Name = MyUDL Set Code page to start = OEM 437: US Leave Expected language blank (because that dropdown doesn’t include UDL in the list) Click the + button under the left panel make sure MyUDL is highlighted in the upper left panel of the dialog Set New filename extension(s) = SMD whether you type in lowercase or uppercase, it ends up uppercase the plugin automatically adds the . prefix when you + the extension you could type another extension and + add it if your UDL has multiple possible extensions Click the + button under the right panel The dialog should look like: [image: 1787174274647-5713f8fa-39a7-4597-b1bf-dc5da4e15e3b-image.jpeg] Close the dialog side notes: It took me a few times to figure out the right sequence, because the plugin’s documentation is a bit sparse, which is why I was explicit as to the right order. If you want to add another group – like an MS-DOS NFO group with the same codepage, but defaulting to the NFO language – you would have to follow similar steps of typing the name, setting the encoding and language, then doing the + – even though it looks like you are editing the MyUDL, as soon as you click + instead of Modify, it will create the new entry instead of modifying the old entry; you then make sure the new entry is selected, and add NFO to its extension list. Create a new file, and immediate right-click the tab and name it blah.smd Notepad++ will automatically apply the UDL, since the UDL extension is set to smd AutoCodepage will automatically apply the OEM-US encoding Open an existing blah.smd file Notepad++ will automatically apply the UDL, since the UDL extension is set to smd AutoCodepage will automatically apply the OEM-US encoding The nice thing about this plugin is that it applies that encoding when you first name, or save-and-name a file, and when you open the file from disk. I believe this should meet your needs, even if no one ever requests or implements the feature in native Notepad++.

@saintleningrad-prog , I had not really thought about embedding encrypted text inside another otherwise unencrypted file. Do you have a specific use case, or example use-cases, in mind? In my opinion, all-or-nothing with encryption generally seems sufficient.

i check both the shortcut and the actual file, and both of them have the “run as administrator” unchecked. so any ideas why it keeps opening in admin mode? No immediate idea. But some questions: How do you normally run Notepad++? With a shortcut on the Desktop? With a shortcut on the toolbar? With the start menu? Or running notepad++.exe by double-clicking the executable? Or by double-clicking a file that is associated with Notepad++? Do they all open it in Admin mode, or just some (and which does which, obviously) inside AppData i have only 3 folders: local, locallow, and roaming When I say %AppData%\Notepad++, I mean that you can paste that directly into the path bar of your Explorer window, and the Windows OS will take you to that location: it knows what is meant by %AppData%, even when you don’t. We’ve got a FAQ: What is %AppData% to help you understand what that really means. If you use the variable %AppData%, it will automatically expand into the C:\users\username\AppData\Roaming or whatever path is appropriate for your computer – there are lots of ways to customize it, and it should be safer to tell a user to use %AppData%\Notepad++ rather than trying to guess that their system is set up exactly as I expect it, so it will probably resolve to C:\users\username\AppData\Roaming\Notepad++, but might not. Unfortunately, while that should be safe to use a variable that has held that meaning for decades, and while general Windows computer experience should have taught users what %AppData% actually means, not everyone does. I should have linked to the FAQ earlier. After reading the FAQ, please try to follow the directions again, this time understanding what I (and the operating system) mean by %AppData% , to find the actual %AppData%\Notepad++\plugins\config directory, confirm that NppFTP exists as a subdirectory, and confirming the permissions that I have requested you to check.

@Coises said: I expect that Version 0.6.5 will fix this. Noted, thanks again, and I’ll let him know — although he actually doesn’t typically use regex for his own purposes.

Search++ version 0.6.5 is available: Update to ICU 78.3 and use static linking for ICU. This is expected to fix problems some testers have had running Search++ on older systems or on minimal Windows installs (like Windows Sandbox). For most users there will be no functional difference between this version and version 0.6.4. Note: There are five icu——.dll files in older versions of Search++ that are not used beginning with version 0.6.5; so it is best to delete the existing Search++ folder (or its contents) before copying, rather than copying the new folder over the old one.

Since it’s essentially working at this point, I’ve renamed the Topic to “BETA” @mpheath , I have updated the README at https://github.com/pryrt/NppPlugin-HiddenLexers to enumerate available options I think I’ll be patient, and give the beta test a while longer, so won’t try to rush to release it before N++ v8.9.8’s PluginsAdmin list is finalized.

1.2.2 Syntax highlighting PowerShell Improved absolute, relative, quoted and unquoted paths colors [image: 1785402977913-paths.png] Improved variables interpolation colors [image: 1785402952228-interpolation.png] [image: 1785402954396-interpolation4.png] Added colors for expressions $(..), ${..} Added registry hives colors (HKLM, HKEY_LOCAL_MACHINE, …) Fixed syntax highlighting Fixed variables colors inside paths and quotes Fixed excessive colors of variables, keywords, and functions enclosed in quotes Fixed unexpected sc.. and vk.. colors in AutoHotkey code Disabled colors for variables inside single quotes ' ' (because single quotes prevents var. interpolation)

@Coises You’re welcome, and thank YOU for promptly creating the new version, and for your plugins in general to begin with! The new one lets me exit without incurring any dialog.

@arnaud-derette said: I does not work in the operator 2 list either (or may be i need to do something more than just put § there ?) Like I said, because you want the § to not have spaces, like in parent§.D, it won’t work for you. § in operators 2 will only work if you can have spaces around the §

@rdipardo thank you for pointing that out. I will check and do the needful.

Thank you again for your help.

@chtaylo3 , You only need to post in the “Support for Plugins Admin & NppPluginList” topic if there’s a feature or bug with the Plugins Admin and the list DLL itself. If there are issues with your PR to add it to NppPluginList, those will be discussed in the PR itself – and it looks like yours has been accepted already. If you want to just announce your new plugin, you can just create a new Topic in the Plugin Category to tell us about it. Hence, I am moving your post to its own Topic. And congrats on creating a lexer plugin!

NppExec v0.8.12.1 has been released! Glory to Ukraine! Glory to the heroes! improved: now WarningAnalyzer automatically removes “” around a file path/name fixed: the Console Output Filters dialog did not clear WarningAnalyzer’s cache improved: now Highlight’s [I], [B], [U] have Italic, Bold and Underline style Get it here: https://github.com/d0vgan/nppexec/releases/tag/NppExec_v08121

@Michael-Vincent Thanks for the feedback ;) fixed with : https://github.com/gcyrillus/nppGitClone/releases/tag/V1.0.1

@Michael-Vincent and anyone reading :) Besides the jokes, i’d like some real feedback about the plugin, the code and mainly about the fact that gemini assisted me … Be critical without trolling, do not be afraid to point out all of the funny code, nonsense and incoherence that a light IA can bring within your code unless there is some goods in it . Good jokes are also welcome ;)