![]() It included a setting bracket-pair-colorizer-2.showBracketsInGutter which does what you'd expect. Before this feature was added to VS Code, I was using this extension. I heard about the bracket pair guide feature a little late, from reading this article, which makes the new feature seem like a complete substitute for similar extensions. So the bracket pair guides are helpful to me for just being able to see at a glance whether I'm still looking at a single block. I use 4 spaces for tabs for this exact purpose, but tab size 2 is the norm in most projects I work on or with. For procedural style modules, sometimes it's a very big file and even though there is a great number of top-level blocks, many are still long enough that the contents can't all fit in the viewport at once. ![]() For me, if I'm working with javascript modules, often there are gonna be a lot of top-level functions, objects, classes, etc. Functionally it's not a huge deal, but sometimes it makes a difference. I believe the inconsistency looks a little sloppy, like it might be an accident (not saying it is, but I usually try to avoid the appearance of unintended behavior). I can understand how it might seem superfluous or even annoying if you're dealing with a large file where everything or almost everything is wrapped in a single bracket pair, like an HTML file (although I think bracket pair guides don't even show for HTML tags by default). Well personally I think showing guides for all lines should be the default behavior, but maybe that's more controversial than I think. I searched vigorously for a setting I might have missed, so I don't think one exists. I did read the changelog for the Oct and Nov updates, and the whole blog post on the new bracket pair colorizer feature. But if you just hit Ctrl+A and Tab, suddenly the bracket pair guide is visible. There is no vertical bracket pair guide visible. In settings.json it's easy to see, as the settings are all in a single object.If both brackets are the first character on the line, their vertical bracket pair guide is invisible. Like, no control characters before the bracket. ![]() Make sure the brackets are not indented at all.A vs code settings file (settings.json) is a good example since you'll need to open it to set these settings anyway. Open a file with brackets and multiple lines between them.Follow the steps outlined in the change log to enable bracket pair guides.Maybe due to window scaling factor + subpixel rounding issues, that seems plausible.ĭoes this issue occur when all extensions are disabled?: Yes So apparently we are looking at a layout bug. Restoring window.zoomLevel and deleting editor.fontFamily instead: Changing the font family or the zoom level somehow breaks rendering of the line. Anyway, I figured out the problem, bizarrely.
0 Comments
Leave a Reply. |