@wessam-moustafa said:

Just wondering whey didn’t you use “Editor.copyText(text) → int”

No good reason for not using that function in this. I think I copied the more complex code from a script I had which was doing something a bit more complicated, and totally unnecessary for swapping clipboard and selected text. Thanks for pointing out the simplification!

@ortomind

There is documentation on how to place search+replace in a macro, here: http://docs.notepad-plus-plus.org/index.php/Editing_Configuration_Files#Search_.2F_Replace_encoding

That may be a bit cryptic, but here’s one example of many that can be found, that show how to implement a real use-case: https://notepad-plus-plus.org/community/topic/11735/notepad-macro-not-working-correctly/2

You can adapt this example (which coincidentally also involves upper/lowercase manipulation!) for what you’re trying to do.

That I have already figured out. That is the reason I asked about a special symbol, which would convert to a space but would not break the keywords parser

Gur,

Works beautifully.

Thank you kindly for all your efforts.

Rest assured your work is much appreciated.

Notepad++ with TagLEET is perfect for a use case like mine: legacy code base with a custom CTAGS language definition. Now, even for a language that’s case insensitive.

There are other wonderful Notepad++ plugins for CTAGS, but they tend to focus on updating and regenerating the tags file. I couldn’t really figure out how to make them work with my TAGS and my .ctags–for the custom language I have to work with. With TagLEET there was literally no effort. Generate the TAGS file in the source code’s current folder or somewhere in an ancestor folder and that’s it.

TagLEET is also brilliantly quick. My TAGS file is 140Mb and I saw no problems as of yet.

Hi Guy038,

Thank you for your response. I decided to update the Notepad++ version by uninstalling the version that was previously installed (which is weird because the previous version installed on the work machine was Notepad++ v7.2.2) and the REGEX function is working fine now.

Cheers,
Arvindran

@guy038 you are the best… you just saved my lots of time. Thanks a lot you don’t know how much did you helped me here.

Thankyou
Thankyou
Thankyou

Using Prefix mode on the Keywords Lists tab might help you to some degree. In one of the groups check Prefix mode and then enter $ in the text box. Finally, click on the Styler button to select the highlight style you want for hex numbers. This will work fine as long as you have some whitespace at the end of your hex numbers. Another limitation is it will highlight "$NotHex " in exactly the same way.

If that works well enough, you can do something similar for “%” and “#”.