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

@Afik-Gilboa said: and I am not doing “run as admin”, at least not on purpose Your Debug Info clearly indicates you are running as Admin, and I believe that your Notepad++ title bar will also say Administrator on it. If you aren’t doing it on purpose, then you need to check your Windows right-click Properties on notepad++.exe and whatever shortcut you are using (on your desktop, task bar, or start menu) and see if one of them has it set to run as Admin in the Compatibility tab (see this recent discussion if you need more on how to check executables or shortcuts for run-as-admin and how to change that). there is no “NppFTP.xml” file in Documents. Ugh. I had forgotten this, because at one point I knew that NPPM_GETPLUGINSCONFIGDIR ignores cloud or settingsDir settings, and instead always uses either AppData or Portable. Annoying “feature” of the message. :-( Sorry for the bad memory. So, anyway, that means that NppFTP should be using %AppData%\Notepad++\plugins\config\NppFTP\ directory, and the NppFTP.xml should be there, instead. So that’s where you should go looking for it. See which of those directories exist, and look at the permissions of the directories and files there.

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 ;)

v0.012 released to CPAN Update for Notpead++ v8.5.4 - v8.9.6.4 Update Editor messages and enumerations (hashes) Update Notepad++ menu commands and messages Remove notepad->prompt() and the Win32::GUI dependency [#91] Please comment on Issue #92 if this call is important to you <https://github.com/pryrt/Win32-Mechanize-NotepadPlusPlus/issues/92> Improve test suite Get it working through Perl v5.42 Don’t test as many old versions (too much compute overhead) See CHANGES file for full history, including interveninng v0.009, v0.010, and v0.011 I don’t always post about new versions here (mostly because I get distracted and forget to). But I thought it was important on this one, because notepad->prompt() has been disabled in this version: if notepad->prompt() is important to you, please comment on https://github.com/pryrt/Win32-Mechanize-NotepadPlusPlus/issues/92 and stick with v0.011, which (until further notice) is the most recent version to include the notepad->prompt()

@medvidec It’s impossible to know for sure without seeing your code, but I doubt the issue has anything to do with Notepad++. If this “global variable” is supposed to be shared between multiple C++ source files, you have to do the following: declare the variable in a header file as extern, e.g.: // your_header.h #include <string> extern const std::string configFile; include “your_header.h” in every source file that uses configFile . provide a definition (at global scope) of configFile in one (and only one) of the source files that includes “your_header.h”: // source_file.cpp #include "your_header.h" // ... const std::string configFile = "/plugins/config/verilogConfig.txt"; // ... You can read about storage class specifiers to learn more.