maybe in future versions, options to:
- highlight just the tagnames rather than entire tags when cursor is inside the tagname only
- highlight a tag's both matching angle brackets when cursor is just outside and adjacent eg: |< or >| or />|
- highlight unmatched (unclosed) tags with a different style
...for ideal operation of this functionality, check out any SynWeb-based editors.

if you get a chance, please add the ability to close the last unclosed tag by typing </

thanks,
Leon

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

i changed the stylers.xml and noticed that the hidden CR LF pairs (when displayed) obey the "default" styling for the active syntax, while tabs and spaces are always black....there simply is no way to change their color, and it's pretty much unusable with a dark background color like the one in "Ruby Blue" stylers.xml on the NP++ download page.

ideally it would be great to be able to style "hidden characters" independent of the "default" syntax color, they are really way too intrusive and hard to distinguish from regular text.

Simple fix: completely update your stylers.xml. It misses the style settings for the whitespace symbols. If you want to ertains your old stylers settings, which I assume is the case here, open the new model file, look for
WidgetStyle name="White space symbol"

and copy it to your stylers.xml (in the correct location ofcourse). Restart and now they should be orange and configurable.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

I would like to take a moment to thank anyone who has worked on this project to date. Stand back and look at the amazing application you have created. Get reinvigorated by the fact that you have made a real difference to many peoples lives and that the impact of what you do may be more than you expect.

My personal heart-felt thank you goes to all who's contribution no matter how small or big have helped. Keep up the good work.

<--- end warning.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

I got the syntax highlight problems on PHP too.
But I don't known whether it is caused by the file name or not. Some of the PHP files with this problem are named like "XXX_1.php", "XXX_2.php", etc.. But I cannot change it back to PHP highlight using the method mentioned by CodeNexus.
And I load those file using "Load Session" function.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

What would be the easiest way to reproduce this behaviour? I tried making a new php file with the same name, add some tags in it and open it in notepad++, it was being highighted.
Any steps I need to do specifically?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

That means your stylers.xml hasnt been updated properly.
if you have a custom stylers file, open the new one and in global styles find the one for tag matching, otherwsie jsut remove your stylers file and notepad++ will make a new one based of the model file.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

The calltips work fine now with case-insensitive sorting in the XML file. But they appear at the very top of the screen for me, rather than near the cursor as expected. Otherwise, everything appears to work fine so far.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Notepad++ makes no use of any threading at all. There are plans to add this but that takes quite a lot of work and time :).

Smart highlighting gets automatically disabled for files larger than 1.5MB, though for complex data a lower value might be needed.
You can disable smart highlighting and use the incremental search or mark search results features instead.

-Harry

If you would like to refer to this comment somewhere else in this project, copy and paste the following link: