mkleehammer
Don't confuse open / close in strings
NOTE: I've not started working on this, so if this is a problem for you, please upvote this by adding a comment or an emoji.
The current algorithm for nested pairs (those where the open and close are different, like parens and braces) simply counts open and cloes as it finds them. But it could be smarter by paying attention to the syntax of each character (ppss).
For example:
(message "finding (, huh?")
---------
If the cursor is anywhere past the paren inside the string, it will incorrectly identify the underlined portion as the pair instead of matching with the first paren before "message".
For this particular case, it would work if we use syntax-ppss and note that we started outside of a string, so we should ignore the paren inside the string. Would work for skipping over comments too.
On a similar note, we could figure out which direction to search for quotes. If we are on a closing quote in a comment and the next quote is not in a comment, we should try the other direction.
Good question @ckruse. I believe it does.
I considered using tree sitter originally, but started with this code since I also use matching inside of strings and quotes.
It might not hurt to use tree-sitter if the point is not in a comment or string, however. It would be foolproof, then. I'll look into that.