@shodanx2 said: the rest of the layout redesign doesn’t have any difficulties except for some the new proposed features You and I will have to disagree on that statement, because I know I cannot convince you, and don’t feel like arguing with you anymore (hence the post that was live for a few minutes before I deleted it; it’s just not worth the effort). But at this point, I want to emphasize @Coises’ earlier suggestion: Make it a plugin at first. Try it out, take it round the block, learn the difficulties with the extra features you want, get it better, get it bulletproof. All the mockups in the world will count as nothing compared to such real-world proof. If people like it, maybe it will be to the 2020s what TextFX was to the 2010s: a plugin that a huge population of users installed, and that they still ask about a decade after the author abandoned it. But if you want suggestions start simple, with just reworking the “look and feel”, without trying to add the extra features like the live count redo your icon design: the industrial/bolted-plate design looks/feels nothing like anything else in Notepad++, so it doesn’t seem like it’s part of the same app. Design some icons similar to the Fluent toolbar icons, and it would at least fit in with one of the existing GUI options.

@PeterJones thanks for the link and information. This is exactly what I wanted. These are some of my notes I put together a while back How to implement Open Source licenses on your software | QuantumWarp So this information will not go to waste, and again thanks for your time.

@rspeicher452 , If you’re always on that screen for that laptop, I would recommend changing Settings > Style Configurator > Language: Global Styles > Style: Default Style to use a bigger font size for the text, so that you don’t have to change the zoom. (The “zoom” feature was designed to be temporary, whereas setting the Default Style font size was designed as the perment way to set text size)

@deleelee , As I said there, the plugin needs to be fixed and a new version released. It’s not a config file for the end user.

@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