how many useless controversies, as usual. I don’t really understand what’s suspicious about my request… I repeat it is a personal file of mine, and it is nothing so evil as it has been painted by those who have started this whole discussion. I really do not understand this totally inappropriate reaction. and perhaps only thing, you are right to say that here many ask for help while perhaps the real intent of this forum is to talk about the notepa++ program, but it is also true that many other users here ask how to solve their problems with reg-ex and other solutions, I am not the only one asking for help on this. Having said that then it is up to you to help or not, responding or not to the various posts. but having said this all the other controversies about a potentially legal file or not i find them really superfluous and useless, as already said a time ago …

Hi All, Continuation … From this last table, we can reasonably ignore : The space and soft hyphen characters Some musical characters All the characters, specific to a language, modern or archaic The tag characters, whose usage is strongly discouraged by the Unicode consortium. In other words, all characters with the No indication, in the To search column, of the previous table ! As a result, we should only take care of this restricted list of 50 characters : •-------•---------•---------------------------------------------•----•------------------•-----• | Code | Abbrev. | Character Name | Cg | N++ Regex | Chr | •-------•---------•---------------------------------------------•----•------------------•-----• | 00A0 | NBSP | NO-BREAK SPACE | Zs | \x{00A0} |   | | | | | | | | | 2000 | NQSP | EN QUAD | Zs | \x{2000} |   | | 2001 | MQSP | EM QUAD | Zs | \x{2001} |   | | 2002 | ENSP | EN SPACE | Zs | \x{2002} |   | | 2003 | EMSP | EM SPACE | Zs | \x{2003} |   | | 2004 | 3/MSP | THREE-PER-EM SPACE | Zs | \x{2004} |   | | 2005 | 4/MSP | FOUR-PER-EM SPACE | Zs | \x{2005} |   | | 2006 | 6/MSP | SIX-PER-EM SPACE | Zs | \x{2006} |   | | 2007 | FSP | FIGURE SPACE | Zs | \x{2007} |   | | 2008 | PSP | PUNCTUATION SPACE | Zs | \x{2008} |   | | 2009 | THSP | THIN SPACE | Zs | \x{2009} |   | | 200A | HSP | HAIR SPACE | Zs | \x{200A} |   | | | | | | | | | 200B | ZWSP | ZERO WIDTH SPACE | Cf | \x{200B} | ​ | | 200C | ZWNJ | ZERO WIDTH NON-JOINER | Cf | \x{200C} | ‌ | | 200D | ZWJ | ZERO WIDTH JOINER | Cf | \x{200D} | ‍ | | 200E | LRM | LEFT-TO-RIGHT MARK | Cf | \x{200E} | ‎ | | 200F | RTM | RIGHT-TO-LEFT MARK | Cf | \x{200F} | ‏ | | 202A | LRE | LEFT-TO-RIGHT EMBEDDING | Cf | \x{202A} | ‪ | | 202B | RLE | RIGHT-TO-LEFT EMBEDDING | Cf | \x{202B} | ‫ | | 202C | PDF | POP DIRECTIONAL FORMATTING | Cf | \x{202C} | ‬ | | 202D | LRO | LEFT-TO-RIGHT OVERRIDE | Cf | \x{202D} | ‭ | | 202E | RLO | RIGHT-TO-LEFT OVERRIDE | Cf | \x{202E} | ‮ | | | | | | | | | 202F | NNBSP | NARROW NO-BREAK SPACE | Zs | \x{202F} |   | | | | | | | | | 205F | MMSP | MEDIUM MATHEMATICAL SPACE | Zs | \x{205F} |   | | | | | | | | | 2060 | WJ | WORD JOINER | Cf | \x{2060} | ⁠ | | | | | | | | | 2061 | (FA) | FUNCTION APPLICATION | Cf | \x{2061} | ⁡ | | 2062 | (IT) | INVISIBLE TIMES | Cf | \x{2062} | ⁢ | | 2063 | (IS) | INVISIBLE SEPARATOR | Cf | \x{2063} | ⁣ | | 2064 | (IP) | INVISIBLE PLUS | Cf | \x{2064} | ⁤ | | | | | | | | | 2066 | LRI | LEFT-TO-RIGHT ISOLATE | Cf | \x{2066} | ⁦ | | 2067 | RLI | RIGHT-TO-LEFT ISOLATE | Cf | \x{2067} | ⁧ | | 2068 | FSI | FIRST STRONG ISOLATE | Cf | \x{2068} | ⁨ | | 2069 | PDI | POP DIRECTIONAL ISOLATE | Cf | \x{2069} | ⁩ | | 206A | ISS | INHIBIT SYMMETRIC SWAPPING | Cf | \x{206A} |  | | 206B | ASS | ACTIVATE SYMMETRIC SWAPPING | Cf | \x{206B} |  | | 206C | IAFS | INHIBIT ARABIC FORM SHAPING | Cf | \x{206C} |  | | 206D | AAFS | ACTIVATE ARABIC FORM SHAPING | Cf | \x{206D} |  | | 206E | NADS | NATIONAL DIGIT SHAPES | Cf | \x{206E} |  | | 206F | NOSP | NOMINAL DIGIT SHAPES | Cf | \x{206F} |  | | | | | | | | | 3000 | IDSP | IDEOGRAPHIC SPACE | Zs | \x{3000} | 　 | | | | | | | | | FEFF | ZWNBSP | ZERO WIDTH NO-BREAK SPACE / BYTE ORDER MARK | Cf | \x{FEFF} |  | | | | | | | | | FFF9 | IAA | INTERLINEAR ANNOTATION ANCHOR | Cf | \x{FFF9} |  | | FFFA | IAS | INTERLINEAR ANNOTATION SEPARATOR | Cf | \x{FFFA} |  | | FFFB | IAT | INTERLINEAR ANNOTATION TERMINATOR | Cf | \x{FFFB} |  | | | | | | | | | FFFC | OBJ | OBJECT REPLACEMENT CHARACTER | So | \x{FFFC} |  | | FFFD | ? | REPLACEMENT CHARACTER | So | \x{FFFD} | � | | | | | | | | | 1BCA0 | (SFLO) | SHORTHAND FORMAT LETTER OVERLAP | Cf | \x{D82F}\x{DCA0} | 𛲠 | | 1BCA1 | (SFCO) | SHORTHAND FORMAT CONTINUING OVERLAP | Cf | \x{D82F}\x{DCA1} | 𛲡 | | 1BCA2 | (SFDS) | SHORTHAND FORMAT DOWN STEP | Cf | \x{D82F}\x{DCA2} | 𛲢 | | 1BCA3 | (SFUS) | SHORTHAND FORMAT UP STEP | Cf | \x{D82F}\x{DCA3} | 𛲣 | •-------•---------•---------------------------------------------•----•------------------•-----• Remark that I added, to that list, the two characters Object Replacement Character \x{FFFC} and Replacement Character \x{FFFD} often used in case of encoding problems ! Then the updated Mark regex would be : MARK [\x{00A0}\x{2000}-\x{200A}\x{200B}-\x{200F}\x{202A}-\x{202E}\x{202F}\x{205F}-\x{206F}\x{3000}\x{FEFF}\x{FFF9}-\x{FFFD}\x{D82F}\x{DCA0}\x{D82F}\x{DCA1}\x{D82F}\x{DCA2}\x{D82F}\x{DCA3}] And the updated Python script is : # -*- coding: utf-8 -*- from Npp import editor, notepad, NOTIFICATION class SRFSC(object): def __init__(self): notepad.callback(self.callback_npp_BUFFERACTIVATED, [NOTIFICATION.BUFFERACTIVATED]) self.callback_npp_BUFFERACTIVATED(None) def callback_npp_BUFFERACTIVATED(self, args): # SPACE chars ( Zs ) editor.setRepresentation(u'\u00A0', "NBSP") # no-break space editor.setRepresentation(u'\u2000', "NQSP") # EN quad editor.setRepresentation(u'\u2001', "MQSP") # EM quad editor.setRepresentation(u'\u2002', "ENSP") # EN space editor.setRepresentation(u'\u2003', "EMSP") # EN space editor.setRepresentation(u'\u2004', "3/MSP") # three-per-EM space editor.setRepresentation(u'\u2005', "4/MSP") # four-per-EM space editor.setRepresentation(u'\u2006', "6/MSP") # six-per-EM space editor.setRepresentation(u'\u2007', "FSP") # figure space editor.setRepresentation(u'\u2008', "PSP") # punctuation space editor.setRepresentation(u'\u2009', "THSP") # thin space editor.setRepresentation(u'\u200A', "HSP") # hair space # FORMAT chars ( Cf ) editor.setRepresentation(u'\u200B', "ZWSP") # zero width space editor.setRepresentation(u'\u200C', "ZWNJ") # zero width non-joiner editor.setRepresentation(u'\u200D', "ZWJ") # zero width joiner editor.setRepresentation(u'\u200E', "LRM") # left-to-right mark editor.setRepresentation(u'\u200F', "RLM") # right-to-left mark editor.setRepresentation(u'\u202A', "LRE") # left-to-right embedding editor.setRepresentation(u'\u202B', "RLE") # right-to-left embedding editor.setRepresentation(u'\u202C', "PDF") # pop directional formatting editor.setRepresentation(u'\u202D', "LRO") # left-to-right override editor.setRepresentation(u'\u202E', "RLO") # right-to-left override # SPACE chars ( Zs ) editor.setRepresentation(u'\u202F', "NNBSP") # narrow no-break space editor.setRepresentation(u'\u205F', "NNBSP") # medium mathematical space # FORMAT chars ( Cf ) editor.setRepresentation(u'\u2060', "WJ") # word joiner ( zero width no-break space ) editor.setRepresentation(u'\u2061', "FA") # function application editor.setRepresentation(u'\u2062', "IT") # invisible times editor.setRepresentation(u'\u2063', "IS") # invisible separator editor.setRepresentation(u'\u2064', "IP") # invisible plus editor.setRepresentation(u'\u2066', "LRI") # left-to-right isolate editor.setRepresentation(u'\u2067', "RLI") # right-to-left isolate editor.setRepresentation(u'\u2068', "FSI") # first strong isolate editor.setRepresentation(u'\u2069', "PDI") # pop directional isolate # FORMAT chars ( Cf ) DEPRECATED editor.setRepresentation(u'\u206A', "ISS") # inhibit symmetric swapping editor.setRepresentation(u'\u206B', "ASS") # activate symmetric swapping editor.setRepresentation(u'\u206C', "IAFS") # inhibit arabic form shaping editor.setRepresentation(u'\u206D', "AAFS") # activate arabic form shaping editor.setRepresentation(u'\u206E', "NADS") # national digit shapes editor.setRepresentation(u'\u206F', "NODS") # nominal digit shapes # SPACE chars ( Zs ) editor.setRepresentation(u'\u3000', "IDSP") # ideographic space # FORMAT chars ( Cf ) SPECIALS editor.setRepresentation(u'\uFEFF', "ZWNBSP") # zero width no-break space : deprecated ( see U+2060 ) / byte order mark editor.setRepresentation(u'\uFFF9', "IAA") # interlinear annotation anchor editor.setRepresentation(u'\uFFFA', "IAS") # interlinear annotation separator editor.setRepresentation(u'\uFFFB', "IAT") # interlinear annotation terminator # OTHER symbols ( So ) editor.setRepresentation(u'\uFFFC', "OBJ") # object replacement character editor.setRepresentation(u'\uFFFD', "<?>") # replacement character # FORMAT chars ( Cf ) # For characters OVER the BMP, with code > FFFF, we can use, EITHER, the syntaxes : # - editor.setRepresentation(u'\U0001BCA0', "SFLO") TRUE "32-bits" representation # - editor.setRepresentation(u'\uD82F\uDCA0', "SFLO") The 16-bits "SURROGATES PAIR" editor.setRepresentation(u'\uD82F\uDCA0', "SFLO") # shorthand format letter overlap editor.setRepresentation(u'\uD82F\uDCA1', "SFCO") # shorthand format continuing overlap editor.setRepresentation(u'\uD82F\uDCA2', "SFDS") # shorthand format down step editor.setRepresentation(u'\uD82F\uDCA3', "SFUS") # shorthand format up step # Active the character representation notepad.menuCommand(MENUCOMMAND.VIEW_ALL_CHARACTERS) notepad.menuCommand(MENUCOMMAND.VIEW_ALL_CHARACTERS) SRFSC() I did not investigate in the S/R, because of the number of chars to handle ( 50 ) and because I’m just feeling… lazy for such a task ! However with the Mark operation, which helps you to locate exactly where are these special characters and the Python script which clearly identify them, you should be safe with your file’s contents ;-)) Best Regards guy038

Hi @Andreas-Trösch The outcome is already in the clipboard or, as you just discovered, you can copy it from the Message box. Glad it helped you!

@Gergely-Apró , The answers you have received are good. If you would like more documentation on this, the official Notepad++ docs talk about the substitution expressions here. Notepad++ uses what’s known as the “Boost engine” (currently v1.70) for handling the regular expressions, and that has its substitution documentation here

Layout a website in pure html with over 3000 pages is complete nonsense! Сms for the site)))

@gstavi said in Windows XP support being dropped...how do people feel?: With all due respect to the hard work being poured into Notepad++, older versions can edit text (or view logs) just fine. There’s some wisdom here. Yea, if you’re going to use an ancient OS that is no longer updated, why get all frazzled about not being able to have its latest version not run? Thus: Run an old OS…run an old N++. Maybe I am overestimating the user community reaction to the devs decision.

Hello, @alan-kilborn and All, Unfortunately, we should have predicted such behavior ! Basically, your regex (?s)(foo\(|\G)((?!\);).)*?\K0x(BA|DE) looks, either : For the literal string foo(, followed by any char till the first literal string 0xBA or 0xDE For any char , right after the previous match ( \G ) till the first literal string 0xBA or 0xDE So, given this sample : 0xBA ( Line A ) 0xBA 0xDE int x = foo(0, 0xBA 0xDE ); ( Line B ) 0xDE 0xBA int x = foo(0, 0xDE 0xBA ); 0xBA 0xDE 0xBA 0xDE int x = foo(0, 0xBA 0xDE ); 0xBA 0xDE Move the caret to the very beginning of line B, for instance. Normally, as the next 0xDE is still outside a function f00 range, it should not be matched. However, it does match this occurrence ! Why ? Because of the combination of the (?s) modifier, which considers any char and the \G assertion : wherever your caret is located, the \G assertion is always true when your first execute your regex . Indeed, in this case, the regex engine considers that a virtual previous occurrence occurred and stopped right before the caret location. So, it will always find the nearest literal string 0xBA or 0xDE, at any location ( refer to the regex (?s)\G.*?0x(BA|DE) ) Luckily, I found out a solution, which supposes that three hypotheses are verified : You must use the N++ version 7.9.1 or a later version, which correctly handles the behavior of the \A assertion You systematically must move the caret to the very beginning of current file ( implicit for a Find All in Current Document, a Find in all Opened Documents or a Find All operation ! ) You must use the (?!\A)\G syntax, in the overall regex ( instead of \G ! ) So the generic regexes, of my previous post, should be improved as : SEARCH (?s)(?:BR|(?!\A)\G)(?:(?!ER).)*?\K(?:SR)    OR    (?-s)(?:BR|(?!\A)\G)(?:(?!ER).)*?\K(?:SR) And gives, for your specific regex : (?xs) (?: foo\( | (?! \A ) \G ) (?: (?! \); ). )*? \K (?: 0x(BA|DE) ) You may verify, with the provided sample, that, at soon as the caret is not at the very beginning of the first line ( Line A ), before running this improved regex, it wrongly matches the two strings 0xBA and the string 0xDE, located before the first foo\( string ! Hence, the necessity to respect the second hypothesis above, which ensures that the \A assertion is true, before regex execution. By this means, the second alternative of BR : (?!\A)\G will not be true, at the first execution of the regex ;-) BR guy038

It makes sense to create an issue to “show non-printable characters in the find dialog” somehow. I assume even if the dialog doesn’t support that character directly, it might be displayed like “·” or something. And that doesn’t necessarily affect the data copied to the clipboard (i.e. it contains Unicode character as is).

@Justin-Gaughan said in Auto indent: and it’s not auto indenting It would maybe help if you said something about your expectation for auto-indenting, if @PeterJones 's explanation does not satisfy.

Thank you for reply.

@Luiza-Henriques Perhaps it would help if you would fully show the text behind your Preferences window? As from what I can see of it, EVERYTHING is underlined and that is not right. Links should be enabled by default, without you having to change any settings.

@VAVoices Does this also happen if you are using npp without plugins installed? Can be tested by using the -noPlugin command line switch.

@storm-Perfect Since no one has replied yet, I assume that the term “power mode” is not clear to everyone, at least it isn’t to me and I don’t want to reinstall VS just to find out what it means. So maybe you can give a brief description of what power mode means?

99% solved, final resume: As usual, there where different issues, complementing each other - from the software and from me … the current user has no admin-rights, so there is the usual problem of admin versus user there was the 32bit of NP++ installed; the update to 64bit did not reset all registry-settings of 32bit I checked the HKLM-settings and thought that this will overwrite the user-settings: my fault, existing user settings stayed alive there where user settings for “.re” which linked to “re_auto_file” which linked to inactive x86-start-commands Now I cleaned up all x86-values to current links, and this enabled the command “Open with … - select Standard application …” again. Now a double-click on .VVA and .RE opens it with NP++ The last “1% cosmetic unsolved” for both file types is that the icon in Explorer is smaller than the standard icon and the file-description is not “Notepad++ Document”. Thanks to all posters for advice!

@PeterJones For writing the settings file I use a Delphi class that encapsulates the handling of INI files. AFAIK this class uses some Windows APIs for INI files (e.g. GetPrivateProfileString). Thus I don’t know if buffered write comes into play when the file is saved. The plugin’s INI file is written when its dialog is closed (the dialog’s window is destroyd as well in this moment). That means the last change of this file happened when you used the plugin for the last time. Thus, I have no clue what could have caused NUL-ing the INI file - especially as you wrote I hadn’t recently made any changes to the ExtSettings through the plugin GUI, so I am not sure why it would have been trying to write/edit the INI yesterday or today. Sorry, I have no idea how this could have happend and how to reproduce this incident.

@gstavi said in search and highlight 2 or more words with different colors: In what way does this improve over right click -> Style token? It really doesn’t. :-) Except that you don’t have to find an occurrence (by hand or search) of your “token” first, in order to rclick it. The script is really just a demo that someone could build something related upon. I can’t see someone typing all those “tokens” very often… It really makes way more sense to use a UDL for such a purpose (OP’s original “log analysis”). And that was my first suggestion to OP. But everyone has their own workflow. And their own likes, dislikes, and "I want"s.

@PeterJones Got it, thanks, I configed in config.xml and it work now

@guy038 Thank you for your hard work. :)

@PeterJones, Thank you! I was sure there had to be a way to do this. I was hoping to avoid using something outside UDL, but I’m glad to know there is a way to deal with this. Gonna take look at it.