vincaslt / vscode-highlight-matching-tag Goto Github PK

Applying custom settings don't seem to be working.

Details can be found here.

Basically:

1. Scope your configurations. They should preferably be resource -scoped where possible.
2. Ensure calls to vscode.workspace.getConfiguration include the resource parameter.

you have good screen shot on Readme page.

what is the color theme used here ?

The extension is unable to find the matching pair, if any of the child element has *ngIf/ngFor on the element tag. '' may be the culprit.

VSCode version: 1.18.0

              <div> <!-- cant find -->
                    <div> <!-- cant find -->
                        <div class="some-class" *ngFor="let bar of bars"> <!-- cant find -->
                            <div class="foo"> <!--works!-->
                                <p>Hello</p> <!--works-->
                            </div>
                            <div class="bar"><!--works!-->
                                <p>Hello</p> <!--works-->
                            </div>
                        </div>
                    </div>
                </div>

After update to 1.15.1 I noticed that after I change something in some React files, I have no longer Eslint or Prettier or some other extensions work correctly. I tried everything: uninstall and install again VS Code, on and off some extensions - nothing helped. I reduced my extensions list to a very small amount and by disabling one by one and checking the result I found who was the killer.

IDK if you could reproduce this issue, but here what I've got:

Linux Mint 18.1 Serena
VS Code 1.15.1

Tested in .js document in React component (~160 lines of code in the file including empty lines)

Console was silent.

Hope you'll fix this issue. For now I have to uninstall it because it totally ruins workflow.

It would be nice to have the matching tags also indicated in the gutter.

The extension is causing a lot of errors with the message "Cannot read property 'opening' of null". The stack trace indicates that it originates at getClosingTag (${User}\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:61:35), which I've found corresponds to this line.

Hi
Thank you, buddy, this extension makes my life much easier.
I just wanted to report a little bug.
it does not work with tags that have Vuejs directives as attributes (or their parent tags).

Hi and thanks for an awesome extension!

One thing I am missing from Sublime's BracketHighlighter is that I can jump from one tag to another with one keyboard shortcut, and also select the content in between tags. VS Code's Bracket Pair Colorizer extension does this but for brackets only,

Could it be possible to implement this feature in your extension as well?

Thanks in advance!

Thank you for your work on this extension!

I've found that some HTML tags embedded in PHP will not show as a match, while others do. For example, in the following PHP snippet from Generate Press theme, I get no match on the first occurring section and main tags. I inserted a pair of section tags towards the end as a test, and I do get a match on this final pair. It seems that when there is an HTML tag with PHP brackets within it, the tag matching fails.

<section id="primary" <?php generate_content_class(); ?>>
    <main id="main" <?php generate_main_class(); ?>>
        <?php do_action('generate_before_main_content'); ?>

        <?php do_action('generate_archive_title'); ?>
        <?php /* Start the Loop */ ?>
        <?php while (have_posts()) :
            the_post(); ?>
        <?php
                get_template_part('content', get_post_format());
            ?>
            <?php endwhile; ?>
            <?php generate_content_nav('nav-below'); ?>
            <?php else : ?>
            <?php get_template_part('no-results', 'archive'); ?>
            <?php endif; ?>
            <?php do_action('generate_after_main_content'); ?>
    </main>
    <section></section>
</section>
<?php
do_action('generate_sidebars');
get_footer();

When there is no match generated as it should, I sometimes get this console error:
[vincaslt.highlight-matching-tag] Cannot read property 'closing' of null: TypeError: Cannot read property 'closing' of null at findClosingTag (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:44:12) at findOpeningTagByPosition (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:74:35) at findOpeningTagByPosition (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:78:20) at findOpeningTag (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:82:12) at findCurrentTag (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:90:11) at vscode.window.onDidChangeTextEditorSelection (C:\Users\Name\.vscode\extensions\vincaslt.highlight-matching-tag-0.4.4\out\src\extension.js:134:28) at e.invoke (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:57853) at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:59575) at e.$acceptSelectionsChanged (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:416364) at t.e.invoke (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:444633) at e._invokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:290588) at e._receiveOneMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:290278) at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:289305 at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:291224 at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:58570 at e.invoke (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:28:57853

Thanks for your help!

Hi, I can't add BackgroundColor, is it impossible to add background-color css?

here's my code

"highlight-matching-tag.leftStyle": { "borderWidth": "0 0 0 1px", "borderStyle": "dotted", "borderColor": "green", "borderRadius": "5px", "background-color": "yellow" }, "highlight-matching-tag.rightStyle": { "borderWidth": "0 1px 0 0", "borderStyle": "dotted", "borderColor": "green", "borderRadius": "5px", "background-color": "yellow" },

The extension stops working whenever I open a file containing html being written by javascript with un error:

[2018-10-24 11:12:48.433] [renderer1] [error] invalid syntax at line 195 col 132:

                                      '<input class="form-check-input" type="checkbox" disabled ' + (v.ativo == 1 ? 'checked' : '')  +
                                                                                                                                 ^: Error: invalid syntax at line 195 col 132:

                                      '<input class="form-check-input" type="checkbox" disabled ' + (v.ativo == 1 ? 'checked' : '')  +
                                                                                                                                 ^
at Lexer.next (C:\Users\Rutenio\.vscode\extensions\vincaslt.highlight-matching-tag-0.7.0\node_modules\moo\moo.js:397:13)
at Object.parseTags (C:\Users\Rutenio\.vscode\extensions\vincaslt.highlight-matching-tag-0.7.0\out\src\tagParser.js:79:36)
at vscode.window.onDidChangeTextEditorSelection (C:\Users\Rutenio\.vscode\extensions\vincaslt.highlight-matching-tag-0.7.0\out\src\extension.js:86:38)
at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:99:496)
at e.$acceptEditorPropertiesChanged (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:589:930)
at t._doInvokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:640:888)
at t._invokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:640:554)
at t._receiveRequest (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:639:126)
at t._receiveOneMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:638:59)
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:635:926
at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:98:138
at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:99:496)
at a (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:154:213)
at Socket._socketDataListener (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:154:432)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

Up till now, the plugin will use almost 100% CPU and will stay in the process even after you've disabled it or close VSCode. You'll have to manually kill the process.

For now, I have to uninstall the plugin and looking at some other alternative.

Insanely huge files with tens of thousand nested tags break the extension due to heap out of memory exception.

This is because matching of the tag starts at the beginning of the file, and only ends with the found match, keeping all other matches in memory. Intermediate matches should somehow not be all held in memory, but rather accessed on demand.

Screenshot: https://i.imgur.com/YcNIp2g.png

The screenshot says it all. Word Wrap is turned on.

My custom settings are:

"highlight-matching-tag.styles": {
    "opening": {
        "full": {
            "custom": {
                "borderWidth": "0 2px 0 2px",
                "borderStyle": "solid",
                "borderColor": "yellow",
                "borderRadius": "5px"
            }
        }
    },
}

Not able to find a conflicting plugin, but this extension just doesn't work anymore for me, on latest version of VSC and extension - Win.10

<div style={{ paddingBottom: 40 }}>
</div>

Is not matched

It will not works on this kind of tag like <div :xx="aa"></div>

I think this also causes #26

• Extension Name: highlight-matching-tag
• Extension Version: 0.4.4
• OS Version: Darwin x64 17.3.0
• VSCode version: 1.19.2

We have written the needed data into your clipboard. Please paste:

{
	"activationTimes": {
		"startup": true,
		"codeLoadingTime": 3,
		"activateCallTime": 0,
		"activateResolvedTime": 0,
		"activationEvent": "*"
	},
	"runtimeErrors": [
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'opening' of null"
		}
	]
}

• Issue Type: Bug
• Extension Name: highlight-matching-tag
• Extension Version: 0.8.5
• OS Version: Darwin x64 18.2.0
• VSCode version: 1.30.1

⚠️ We have written the needed data into your clipboard. Please paste! ⚠️

• Extension Name: highlight-matching-tag
• Extension Version: 0.4.4
• OS Version: Windows_NT x64 10.0.16299
• VSCode version: 1.19.2

We have written the needed data into your clipboard. Please paste:

{
	"activationTimes": {
		"startup": true,
		"codeLoadingTime": 1,
		"activateCallTime": 0,
		"activateResolvedTime": 0,
		"activationEvent": "*"
	},
	"runtimeErrors": [
		{
			"name": "TypeError",
			"message": "Cannot read property 'closing' of null"
		}
	]
}

For example:

<div onClick={() => foo()}>
</div>

The tag matcher thinks the tag ends at the > in () =>. usually this doesn't matter much, but it can when you have a self-closing tag:

<div>
<div onClick={() => foo()} />
</div>

Because of that inner div's arrow function, the extension thinks that the inner div is a regular tag instead of a self-closing tag, and thus shows the bottom </div> as the matched tag.

I suppose the easiest solution would be to count {}s, ()s, and probably ""s inside of tag attributes and only honor a > as tag syntax if all other brackets are balanced.

After a lot of debugging I found my "Code Helper" process was running at 100% CPU usage due to this plugin.

The issue seems to be an input tag with a ref attribute while working in a .vue file

<input ref="input" /> will cause this to hang while <input /> is just fine

• Extension Name: highlight-matching-tag
• Extension Version: 0.5.0
• OS Version: Darwin x64 17.5.0
• VSCode version: 1.27.2

We have written the needed data into your clipboard. Please paste:

Hello,
How can i have underlined Html Tag like in Sublime Text (BracketHighlighter plugin) ?
Best regards

I use the Colorize Bracket extension but it can't really handle tags in HTML or PHP but this thing does just the trick. Thank you so much @vincaslt

If a colon is used in an html element attribute (required for Vue v-bind directives), it breaks highlighting. Perhaps related to #7?

Thank you for an absolutely essential extension!

Is it possible to configure this extension to work with other file extensions? I really like it for html and would like to get it working for html.erb file extensions.

I'm pretty new to VSCode so maybe there's a setting that I'm missing?

Hi!,

I have run into a little bug with your package. On save, a new status pops up on the bottom tool bar saying 'Running Save Participants'. I think there is more but I can't make it out.

It only seems to happen on random files and so far only on large blade.php files.

Its causing my sftp sync package to not upload. I have uninstalled every single package except sftp and it went away. Once I re installed your package the issue came right back.

Have you ever run into this or is there a setting to disable whatever is happening?

Thank you!!

I'd like to be able to use this with ejs files too - is this possible?

It works quickly for me in small files. But in a JSX file with 1000+ lines of code, it takes about 2 seconds for it to highlight appropriate tag. Is this considered normal?

VS Code
Version: 1.27.2 (user setup)
Commit: f46c4c469d6e6d8c46f268d1553c5dc4b475840f
Date: 2018-09-12T16:17:45.060Z
Electron: 2.0.7
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
windows 8.1

highlight-matching-tag v 0.4.4

all extensions freeze/hang each time open vue file (*.vue)
after disable highlight-matching-tag extension.
everything work fine.

• Issue Type: Bug
• Extension Name: highlight-matching-tag
• Extension Version: 0.8.6
• OS Version: Darwin x64 18.2.0
• VSCode version: 1.30.2

{
	"activationTimes": {
		"startup": false,
		"codeLoadingTime": 213,
		"activateCallTime": 1,
		"activateResolvedTime": 8,
		"activationEvent": "onLanguage:javascriptreact"
	},
	"runtimeErrors": [
		{
			"name": "SyntaxError",
			"message": "Unexpected token, expected \",\" (17:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unterminated JSX contents (66:9)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (72:108)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (72:106)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (76:105)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (87:90)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (84:87)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (87:90)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (75:7)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (75:7)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (75:7)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (23:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (23:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (24:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (25:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (71:30)"
		},
		{
			"name": "TypeError",
			"message": "Cannot read property 'startsWith' of undefined"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token, expected \",\" (112:15)"
		},
		{
			"name": "SyntaxError",
			"message": "JSX attributes must only be assigned a non-empty expression (78:69)"
		},
		{
			"name": "Error",
			"message": "DebounceError"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (119:3)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (125:3)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token, expected \",\" (121:10)"
		},
		{
			"name": "SyntaxError",
			"message": "Adjacent JSX elements must be wrapped in an enclosing tag. Did you want a JSX fragment <>...</>? (72:3)"
		},
		{
			"name": "SyntaxError",
			"message": "Expected corresponding JSX closing tag for <ulc> (113:2)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (24:1)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token, expected \"}\" (36:101)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (23:16)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token, expected \"=\" (5:19)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (23:16)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (23:16)"
		},
		{
			"name": "SyntaxError",
			"message": "Unexpected token (91:32)"
		}
	]
}

Latest update makes CPU go crazy, and for whatever reason kills vs-code integrated emmet functionality, I tested and disabled all extensions and debugged one by one so I'm petty sure the issue is on this addon.

This plugin makes the whole tag with attribute value(s) highlighted! This prevents in seeing the block of text I'm trying to copy/cut as the background color remains same. I'm using the following values -

"highlight-matching-tag.leftStyle": false,
"highlight-matching-tag.rightStyle": false,
"highlight-matching-tag.style": {
"borderRadius": "2px",
"backgroundColor": "#34495e",
},

Testcase (cursor at | position):

<di|v>
  <input type="button">
</div>

Hi @vincaslt .. you're right if it works .. not seen with the naked eye .. just highlights the opening tags. Thanks and good work.

The plugin is not working on vs code version 1.19.2

Was working perfectly fine in 1.19.1

I am very regularly getting an invalid syntax error in CFML files. This most often occurs within <cfset tags, perhaps because the content does not follow the standard attribute/value structure of most tags. Here is a simple example of one of the lines that triggers it: <cfset someFileHash = hash(someFile, "SHA-512")>.

Here is the full error:

ERR invalid syntax at line XX col XXX:

<code line here>

at Lexer.next (C:\Users\<User>\.vscode\extensions\vincaslt.highlight-matching-tag-0.6.1\node_modules\moo\moo.js:397:13)
at Object.parseTags (C:\Users\<User>\.vscode\extensions\vincaslt.highlight-matching-tag-0.6.1\out\src\tagParser.js:79:36)
at Object.findMatchingTag (C:\Users\<User>\.vscode\extensions\vincaslt.highlight-matching-tag-0.6.1\out\src\tagMatcher.js:12:34)
at vscode.window.onDidChangeTextEditorSelection (C:\Users\<User>\.vscode\extensions\vincaslt.highlight-matching-tag-0.6.1\out\src\extension.js:80:36)
at e.fire (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:99:496)
at e.$acceptEditorPropertiesChanged (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:589:930)
at t._doInvokeHandler (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:640:888)
at t._invokeHandler (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:640:554)
at t._receiveRequest (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:639:126)
at t._receiveOneMessage (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:638:59)
at c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:635:926
at c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:98:138
at e.fire (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:99:496)
at a (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:154:213)
at Socket.n._socketDataListener (c:\Users\<User>\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:154:432)
at emitOne (events.js:116:13)
at Socket.emit (events.js:211:7)
at addChunk (_stream_readable.js:263:12)
at readableAddChunk (_stream_readable.js:250:11)
at Socket.Readable.push (_stream_readable.js:208:10)
at Pipe.onread (net.js:594:20)

Considering the scope of this extension, it doesn't seem necessary that it would need to parse the content of the tag aside from identifying strings to ignore.

It's running just .html file exentesions.
I'm trying in .twig file extensions It's does not work.

This code crash:
<div class=\"myclass\"></div>

use this extension, suggetsion very slow, when disable this extension, it is very quickly

Invalid argument: Error: Invalid argument at t._validatePosition (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:230616) at t._offsetAt (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:229960) at Object.offsetAt (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:228329) at getTextAfter (C:\Users\admin\.vscode-insiders\extensions\vincaslt.highlight-matching-tag-0.3.0\out\src\extension.js:5:60) at getClosingTag (C:\Users\admin\.vscode-insiders\extensions\vincaslt.highlight-matching-tag-0.3.0\out\src\extension.js:48:27) at findClosingTag (C:\Users\admin\.vscode-insiders\extensions\vincaslt.highlight-matching-tag-0.3.0\out\src\extension.js:67:46) at findCurrentTag (C:\Users\admin\.vscode-insiders\extensions\vincaslt.highlight-matching-tag-0.3.0\out\src\extension.js:87:16) at vscode.window.onDidChangeTextEditorSelection (C:\Users\admin\.vscode-insiders\extensions\vincaslt.highlight-matching-tag-0.3.0\out\src\extension.js:132:49) at e.invoke (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:30930) at e.fire (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:34737) at t.$acceptSelectionsChanged (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:347776) at t.e.handle (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:266430) at s (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:154933) at h (c:\Program Files (x86)\Microsoft VS Code Insiders\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:155610) at _combinedTickCallback (internal/process/next_tick.js:67:7) at process._tickCallback (internal/process/next_tick.js:98:9)

After using it for a while my CPU gets maxed out until i kill the extension process

Hi, and thanks a lot for including my previous two requests so speedily.

Probably this will be my last one. I just saw recently the need of selecting not only the contents of matching tag pair but also the content+tag (basically the whole thing between matching pairs including the tag). Could it be possible to have a command for this as well? So to have two commands, the current for content only, and one for content+tag.

Thanks in advance!

I'm using this extension with VSCode VIM, VSCode get frozen when the cursor moved inside of the JSX part of this code snippets:

class Game extends React.PureComponent<IProps> {
    render(): JSX.Element {
        const { isMobile }: IProps = this.props;
        return (
            <Carousel
                dots={!isMobile}
                slidesToShow={isMobile ? 1.5 : 3}
                slidesToScroll={isMobile ? 1.5 : 3}
                dotsClass="game-dots"
                arrows={!isMobile}
                prevArrow={<div>{'<'}</div>}
                nextArrow={<div>{'>'}</div>}
            >
            </Carousel>
        );
    }
}

Tested in VSCode Insiders, with only VSCode VIM & Highlight Matching Tag installed, no extra settings applied.

After disabling or uninstalling HMT VSCode won't get frozen, thus I think HMT causes this issue.

Interestingly, if I did one of the following adjustment, VSCode won't get frozen:

• remove the curly braces {...} inside of prevArrow prop.
• remove any prop before prevArrow prop.
• or Disabling VSCode VIM

I know it's a very weird issue, but I hope it make sense.

Would it be possible to add support for matching <cfif> tags? Example of the issue seen below:

Thanks
Morgan

Hey @vincaslt ! I'm super stoked that you worked on a fix for #5 , but sadly I have to report that it seems to have introduced a different issue with JSX: now tags that have dots in them are breaking the parser. This happens when code imports a module and uses a qualified name to specify the tag:

import * as CV from './CommonView';

function foo() {
    return <CV.Whatever><span>Hi!</span></CV.Whatever>;
}

This is also breaking when any child has a tag that is prefixed by the parent tag, then followed by a dotted name after. I realize that's a confusing formulation, here's an example:

function foo() {
    return <X><X.Whatever /></X>;
}

In this example the <X> doesn't match with the </X>. I'm noticing this when using certain libraries like react.semantic-ui.com, which nests component classes, so you use stuff like:

function foo() {
    return <Form><Form.Button>Submit</Form.Button></Form>;
}

It think that neither of these behaviors happened before the latest release (i.e. the tags would match properly as long as there was no => confusing it), but I'm not 100% certain.

If you're not interested in supporting JSX I understand, I just thought I'd let you know!

Basically I would like to have matching tag highlighting when the cursor is somewhere in the content in the middle of the two matching tags (if nested tags, then the nearest two matching tags). Example:

<div><p>Some where in {cursor here} between</p></div>

So the <p> and </p> tags would be highlighted in this case.

Wonder if this is possible, as I could select the whole content inside the tag without traveling all the way adjacent to either of the two matching tags.

Thanks in advance!

Enabling the extension makes the cursor gets stuck for like 2 minutes and then VS code goes to not responding state and have to restart to get it to working again.