Add check for escaped brackets in levelpos calculation

[cbcoutinho]

Really simple way to fix #532

[cbcoutinho]

@phy1729 Could you comment on these tests so far? I'm not sure how to test the difference between single quotes and double quotes. I'm also unclear how you implement the multi-line test from your comment as well

[phy1729]

I'd use single quotes instead of dollar quotes (e.g. BUFFER='echo (x\])'), but that's just style.

What I was trying to convey before was instead of adding conditionals in brackets-highlighter.zsh, you could add under line 56 or so

\\)
(( SOME_VAR )) && pos++
;;

where SOME_VAR is a placeholder for a variable a user could set to opt-in to the behavior (or opt-out. I don't use the brackets highlighter, so I don't have a strong opinion on what the default should be.)

[danielshahaf]

@cbcoutinho Why close this?

[cbcoutinho]

I accidentally borked a rebase/force push, and gh closed it automatically... Oops. I'll re-commit the changes and open it up again. Op ma 1 okt. 2018 17:10 schreef Daniel Shahaf <[email protected]>:

…

@cbcoutinho <https://github.com/cbcoutinho> Why close this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#533 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AMTd7Fxry7P1jXe_rWkAVgt7r3exgzY3ks5ugjBzgaJpZM4WqIq7> .