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 §

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.

I randomly found this new meta SPDX-License-Identifier: where you can add one line. // Copyright (c) 2026 Jane Smith // SPDX-License-Identifier: MIT https://spdx.org/licenses/ https://spdx.dev/learn/handling-license-info/ https://github.com/david-a-wheeler/spdx-tutorial Thought I might mention this as I have never heard of this standard. I assume it is still legal but, IANAL.

@PeterJones It all sounded so logical to me when I wrote it, but now that I’m reading it again, I have to agree with you— that wasn’t my best explanation of how this is supposed to work. Thanks for clarifying, and yes, Prefer installed Python libraries and a local Python installation are necessary in this scenario. Regarding sys.path, yes, that makes sense. I should have tested all of this in a sandbox; then I would have noticed how my own setup differs from a standard installation. And yes, the procedure, which is ONLY necessary to debug PythonScript scripts, is that you have one Npp instance, in which the script is debugged—let’s call it instance A—and another, let’s call this instance B, in which the script to be debugged actually runs. So, Instance A starts the debugging session via Plugins->NppDebugger->Start. This results in a new Npp instance B being launched. Now, in Instance B, the script that configures debugpy must be started. This causes debugpy to launch another Python process pydevd which is the real python debugger. This means that NppDebugger, from Npp instance A, waits for debugpy in Npp instance B to start the Python debugger pydevd AND for debugpy to start a TCP server to which NppDebugger can then connect. NppDebugger(tcp client) <-> debugy(tcp server) <-intern-> debugy(tcp client) <-> pydevd(tcp server) As soon as NppDebugger establishes a connection, it begins communicating with debugpy via DAP messages. Is the long-term plan … Yes, ultimately, the plugin should be designed to minimize the need for manual configuration editing. For debuggers that work with compiled source code, such as gdb, delve, lldb, etc., this is usually a project-specific setting and something that a user must set at least once per project. I don’t see how the plugin could figure this out on its own. For PythonScript debugging, a simple variable substitution, as you mentioned, seems sufficient. @Lycan-Thrope said: They have a Trial Version If I find the time, I’ll give it a try… but that might take a while… :) @Lycan-Thrope said: What the heck, … :D - thank you :D

@Em776102 not sure what your use is, for example in termux on android you can use nano. For most quick edits it’s enough I guess… Need something more advanced, use: Acode - code editor | OSS Surely it’s not our beloved notepad++, but quick search may reveal even more alternatives.

@Abdellah-Hss Hello thanks for this input, I thought I had to provide all system versions in order to be accepted to admin plugin list. Today I’ve added ARM64 version and will fork the admin list to update it asap. Thanks for the feedback I actually didn’t know the way to publish it via official channel. Hopefully once I get through with this process it will make the list and be easier accesible. Edit I’ve just added the plugin to official list on x86, x64 and ARM64. Till the next update you can only install it via dll or bat installer I provided on github.

@Geoff-Taylor , That is the effect of one of the “security fixes” that prompted v8.9.6.1’s existence. See my reply to see more of the implications of the security changes, and note the discussion it spawned

This issue is one of the most consistently duplicated on the forum, for example: “Highlight HTML and CSS” “CSS comments should be in GREEN” “css formatting not working on embed style sheet…” etc. @peterjones’s initial reply is the correct one. You can also refer to this more detailed explanation regarding the current limitations of Lexilla. For now, a relatively simple way to edit HTML documents with embedded style and script highlighting is to use the tree-sitter plugin. Note that only “light” style themes are currently supported, and you will have to manually download and extract the configuration files to get it working. [image: 1779564282293-npptreesitter-v110.png]