@Claudia-Frank I removed the old installation and I have installed Plugin manually and now run very well !! thank you very much you are super :)

Hi Eric,

I faced just the same problem / challenge. After some testing with various tools I finally ended up with TyperTask (http://www.vtaskstudio.com/support.php). I works pretty well and I am very flexible - it doesn’t belong to a specific application. Now I can use this kind of function where ever I type right now.
I think even PortableApps.com published a version of it.
Good luck,
Ralf

Hello Camilo,

In addition to the Claudia’s Search/Replacement, we could simplify and shorten a bit this S/R, as below :

Notes :

^ represents the classical assertion Start of line

(?:.+?,){3} represents a non-capturing group, repeated three times, exactly, in order to go through the first three columns. This group is the smallest range of standard characters, with its comma delimiter

The \K syntax forces the regex engine to forget any previous match of the regex

So, the remainder, (.+?,)(.+?),, is the final match, which gets the 4th column along with the comma delimiter AND the 5th column, without its comma delimiter

In replacement, the syntax \2 \1 just swaps these two columns, with a space between them

IMPORTANT :

As the \K form is used, your MUST perform a global replacement, clicking on the Replace All button.

The Step by Step replacement, with the Replace button, does nothing, in that specific case ( N++ bug ) !

Best regards,

guy038

I have now used the compare 1.5.6.7 without any problem, as compared to the plugin manager normal download. Now it works as it is supposed to and a big relief.
Why is it simple things get overlooked. Thanks for help resolving.

Well, I don’t know exactly what’s happening, but I think I have some useful insight. You were right that the problem was tied to the UDL “AutoHotKey” (which is not authored by me). So I checked the XML file that defines that UDL, and noticed that every style in the <styles> section had a fontName specified, and that the font specified was not a font on my system.

In the “Define your language…” dialog within NPP, all the “Styler” buttons were leading to dialogs with “Font options” -> “Name” being blank, which I assumed to mean “use the default style”. However it appears that NPP is NOT using the default style when it doesn’t recognise the font specified in the XML file. Why or even if that leads to the strange bracket-matching behaviour above, I don’t know.

For now, I have removed those fontName specs from the AutoHotKey UDL on my system, and NPP now uses the default font as expected, so everything is fine.

I hope this information can help lead to the bug being tracked down.

WPB

Hello @Quitch,

can you check the session.xml file and see it the proper language has been set.
If yes, can you post it?

Cheers
Claudia