-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose bracket matching functionality to extensions #7177
Comments
fyi @alexandrudima |
Sorry, but that won't happen in July |
How about December? 😉 |
How about a PR? |
Alright, but if I make a PR on vscode you have to make a PR on vscodevim. It's only fair! 😉 |
For your proposed API
Thoughts on including it, or should I make a separate request/issue? |
here |
No, I haven't worked on this. Sorry I missed your question almost a month ago. |
Using the above api it would be possible to expose getting the bracket types for a document, and then being able to search surrounding brackets based on the bracket type. The reason for needing vscode to do this work rather then parse it extension side is because we can't tell if a bracket is in a comment or a string without having to implement language specific parsing, while we want a generic solution for all languages. I'm hoping that some of the logic in |
cc @alexandrudima who knows more about this. |
This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding! |
I'm developing a Vim extension for Visual Studio Code and I could really use your guys' bracket matching logic.
Either exposing a function like
getTextDecorations()
or, better yet, a function likegetMatchingBracket(position: Position)
would be awesome.Thanks!
The text was updated successfully, but these errors were encountered: