Under the Tools menu there are a few options for "matching bracers". All bracer matching is done on any {, }, (, or ) type bracers. The first three menu choices are pretty basic, they are:

--Find Next Bracer (reverse) -- Hotkey is: Ctrl+[. This will simple search for the next bracer towards the start of the file from your current cursor location. On finding a bracer it's highlighted and the cursor is positioned at (before) the found bracer.

--Find Next Bracer (forward) -- Hotkey is: Ctrl+]. The opposite of the above function, looks for next bracer until the EOF is hit.

--Find Matching Bracer -- Hotkey is: Ctrl+\. This will look for a bracer match for the bracer your cursor is currently at. It will search forwards or reverse, depending upon the parent bracer (one you're starting from).

A lot more intensive is the final bracer matching menu choice:
--Selected Text Bracer Check -- Hotkey is: F12. This is fairly intensive and thorough. First you need to select some text.

While you can select multiple commands, or even the entire document, I strongly suggest selecting only single commands. This will avoid any potential bracer matches that might "match" but are in two seperate command structures.

The Selected Text Bracer Check works like this:
It starts from the start of the selection, and searches forward for any {,}, (, or ). Once it finds a bracer it searches in the appropriate direction for a match. If a match is found, it moves on to the next bracer. This continues until the end of the selection is hit, or until no match is found. If no match is found a dialog will pop up allowing you to Continue Checking, or to Cancel. If you choose to cancel the last mis-matched bracer found is highlighted. If you continue to run it and no mismatched bracer were found, then nothing is highlighted. If mismatch(es) were found, but you Continued Checking, then the last found mismatch is highlighted.

Right now I have it visually showing it's progress, it can get a little goofy because the rtf box redraws itself pretty poorly. But at least it's an indication that something's going on. I'll probably add a switch to turn off the visual queues, but still highlight any mismatches it finds. Thus speeding up the process up considerably. (Personally I like the visual indicator)

On huge commands with tons of bracers it will be a little slow (depending on your comp as well). But it's not unbearable. Again, it checks EVERY bracer in the command for a match, so you'll see the cursor jumping all over the place from time to time.
