News for hackers. Stuff that matters.

A comment on How VSCode made bracket pair colorization 10,000x faster. Parent comment

Re:How VSCode made bracket pair colorization 10,000x faster by bilalq on Thursday June 22, 2023 @12:49PM (#36435053)
Maybe blindingly obvious in hind-sight, but none of the IDEs I mentioned in my last comment have this feature. Nor does any other IDE I've ever used. It's not hard to imagine why a novel feature, without much prior art, potentially sitting on the blocking path for UI rendering, and contributed by an external person would face friction in being merged into core. Not to mention the onboarding complexity of making a change like this in core vs as a standalone extension for a new contributor.

Also, I don't understand at all what your last sentence there means.

[ Parent | on HN ]
Re:How VSCode made bracket pair colorization 10,000x faster by b5n on Thursday June 22, 2023 @01:22PM (#36435588)
It's always entertaining to me to see 'new'(ish) IDE features being lauded that have already been available in emacs for years, if not decades.
[ Parent | on HN ]
Re:How VSCode made bracket pair colorization 10,000x faster by vladvasiliu on Thursday June 22, 2023 @01:24PM (#36435608)
After a quick search through the settings, IntelliJ seems to indeed not have bracket colorization. I seem to remember there was an option for this, but it may have been a 3rd party plugin.

However, it has something that I find superior: when you're on a bracket, it will highlight its opposing bracket (closing if you're on opening, and vice versa).

The reason I think it's superior is that you can see directly which specific bracket you're looking for, you don't have to hunt for the corresponding shade. And in case your brackets are unbalanced, you'll see it directly.

[ Parent | on HN ]