@PeterJones
Yes, you found it -I had followed the sourceforge link from https://github.com/vinsworldcom/nppConsole, as i could not found any bin file on the github (i am new to github, really…).
I will try 1.2.8.1.

Thanks

Hi, @coises,

That’s really kind of you to ask for my permission.But, considering all the times you’ve listened to me, the least I can do is, of course, give you my full permission to use this file ;-))

Just note that I noticed, at the very end of the ICU.txt file, a small section that I used to verify if the \p{...} syntaxes were written correctly

As this part should not be part of the file, I modified the current file which, of course, changed the sharing link ! And I’ve just updated this link in my previous post !

Best Regards,

guy038

@martin-honnen ,

Please be careful when forking and keeping the original name for an apparently-abandoned plugin. Sometimes, it turns out it wasn’t as abandoned as thought – something like that happened with NppConsole plugin (as obliquely mentioned in a recent Topic here): a few years ago, it appeared abandoned, so a regular here took the source code, and made their own fork, but kept the original name (thinking it would be safe, because it appeared to be no longer supported in the original channel); but then, fast forward a few more years, and the original author did provide their own upgrades to the original plugin – so now there are two competing development paths, each having version numbers not present in the chain for the other, which will make any future questions in the forum confusing, as to which NppConsole plugin is actually being talked about.

Similarly, if morbac ever decides to come back to the plugin, then your fork and the original could have conflicting and/or confusing version numbers and naming.

I would highly recommend coming up with your own name for your product, if you are planning to continue development and support on your version of the plugin. If it’s really just a one-off thing, and you aren’t planning on future bugfixes/improvements/support, then it’s up to you whether it’s worth the rename; but if you want to continue to work on the plugin, then I’d suggest the rename.

OTOH: if you can get permission from @morbac to take over completely, then it’s safe to keep the original name, because you’ve got the permission. (It’s most clear, in cases like that, if you can get write permission to the original repo – @chcg was able to do with @bruderstein’s PythonScript, and that sense of continuity makes it more obvious that his is still the “official” PythonScript.)

@mapsonx ,

I don’t know that tool, so I don’t know what it considers a “critical event”, or what “stopped working” means.

You also don’t say what version of Notepad++ you are using (especially whether or not you are still using the portableapps modification or the official), nor what plugins you may have installed (which can highly affect stability).

But in my experience, Notepad++ doesn’t just “stop working”, except in cases of rare critical bugs, or plugin misbehavior, or user error.

update: Wow, I’d never heard of the Windows Reliability Monitor before. On mine, I see no Notepad++ events. On the events that I do have, some show a “View technical details” link, which brings a crash report which has meaningful information: it’s too bad that yours don’t appear to have that link. The format of that window appears similar to the details obtainable from the Event Viewer – so maybe you can find details for one or more of those evens from that MS tool, and see if that gives you any hints, or share the details so that someone here might be able to give you insight (I know that @xomx has been able to help interpret Event Viewer details before, and that has even led quickly to a PR to fix the bug).