Sublime Forum

**pyparadigm** · January 13, 2016, 6:41am

Did some bug fixes and added multi select support.

Ctrl + Click multiple elements at a time.

**pyparadigm** · January 13, 2016, 6:42am

Added ability to customize highlight settings.

**skaet** · January 13, 2016, 6:42am

I’m getting some interesting performance issues that are easy to reproduce in context but difficult to isolate to submit an issue.

The problem seems to be happen when opening a tag in a particular place, causing ST2 to hang for an extended period and use 50% CPU during that time. I’ll update this with more information after further testing.

**dsarch** · January 13, 2016, 6:42am

I had the same problems today when editing a looooooog ruby file. When i tried to do some search, Sublime just hang and used 100% of cpu.

**clive078** · January 13, 2016, 6:42am

+1 SublimeTagmatcher seems to have a problem editing large files. ST2 started hanging (after installing couple of plugins) when editing very long files, so I moved my ‘Packages’ folder, restarted ST2 (simulating a fresh install) and then I started dropping each plugin one after the other (editing a long css file each time i restarted ST2), every thing was fine until I dropped in the SublimeTagmatcher plugin, ST2 started hanging when editing the long file (using almost 100% of cpu).

**oriceon** · January 13, 2016, 6:43am

I have this problem too. This happens with Sublime Brackets too.

**skaet** · January 13, 2016, 6:43am

Yes, I have found that html and css files of only a few hundred lines are having issues. However, some tags don’t cause the hangups while others do. I mentioned it was hard to pinpoint exactly what and where the problem lies, as well as how to reproduce it reliably between different files.

**thinkkesho** · January 13, 2016, 6:43am

I registered just to say thank you for developing this. It has been the main reason for me not switching over from notepad++ and if all bugs can be resolved, I may make the jump.

Thanks again!

**deadark** · January 13, 2016, 6:43am

Hi all!

As others said before this is a really cool and usefull plugin, and after testing it I have the same problem: With large files it relentizes a lot the editor. I think in files with more than 100 lines aprox. it starts to be really slowly. I don’t know if it will be solved in future versions or if it’s not possible.

Anyway, one possible ‘fast’ solution:

It’s possible to have something like an ‘extensions blacklist’ where put some extension files where don’t execute the plugin? It would be really nice, because in my case I have really long css files but smaller templates files. And where I find really usefull this plugin is with the templates files.

Thanks!!

**mehigh** · January 13, 2016, 6:43am

Thanks for the neat plug-in. Makes finding ‘that missing ending tag’ much easier!

**mehigh** · January 13, 2016, 6:46am

Thought to provide some feedback on this.
On large CSS files (7000 lines for an example), typing in new code is veery slow with this plug-in enabled.
Tried this on both OSX and Windows 7 and it behaves the same on both platforms, even on powerful systems.

Is this checking for the matching tags at each key-stroke ?
Just wondering which would be the best patch for this behavior, such that other users can use it without any blockers.

Let me know your thoughts on this.

**iamntz** · January 13, 2016, 6:46am

Having a 7000 lines css file is an issue by itself, no matter what plugins or editor are you using.

**facelessuser** · January 13, 2016, 6:46am

The problem with this plugin and large files is currently how this plugin is implemented. It currently searches until it finds a match, so if you are between two brackets that are not far apart, then it is quick. If you are between no brackets in a large file, you will search the entire 7000 lines every time you move your cursor.

It is incorrect to say that it is something you just have to live with. I have created a branch that merged sublimeBracket and sublimeTagmatcher and does not have this problem. I fixed it by one: debouncing the events that trigger searching, two: implementing a search threshold so that by default you only search so far, and three: I allow blacklisting certain languages for matching via settings (you will never need to search for tags in CSS); if you would like to search the entire file until you find a match, that has been attached to an on demand shortcut.

**natebeaty** · January 13, 2016, 6:46am

This cracked me up. That’s a whole lotta stylin’!

**mehigh** · January 13, 2016, 6:49am

Confirming on the behavior of facelessuser’s plug-in - everything works like a breeze no matter the size of the file it’s being used in.
( github.com/facelessuser/BracketHighlighter )
Thanks heaps !

And to be honest, I’ve worked on websites where the CSS file had gone beyond the 15K lines limit, so this project wasn’t too big (details require serious work unfortunately, but thank god for ZenCoding and all these helpful little snippets which make our life easier).

**agassi** · January 13, 2016, 6:52am

thank you!
awesome plugin