VSCode handling unbalanced brackets within comments
geor...@bigpond.net.au
Ben
In Andrew’s extempore_lang.xtm
https://github.com/digego/extempore/blob/master/examples/core/extempore_lang.xtm
There is a comment at line 316
;; so back to double for us :(
the unbalanced bracket throws the formatter of Visual Studio Code out of sync from that point in the file onwards. Code indenting goes haywire.
Similarly some comments within example code or in Guides where brackets are balanced but the matching bracket is on a new line have the same effect. This often happens where the writer makes an “aside comment” within the text and the matching bracket occurs in the next line. I usually change these aside brackets to dashes when I find them.
I know it is a minor point and you have more than enough to do but I think the formatter/parser could be told to ignore brackets within commented-out text. I don't know how to do that.
Regards
George
Ben Swift
Ah, bummer. I've pushed a temporary fix, will think about a better one asap.
https://github.com/digego/extempore/commit/010ae8fa46fd66f020c7e379b7e0429d050a16c0
Cheers,
Ben