Proposal: Ability not to auto-close comments

[erichiller]

As far as I can tell this is not currently available.

Oftentimes I need to comment out blocks of code and use /** and immediately a */ auto inserted resulting in one extra step. Not a huge deal by any means, but it would be a nice added feature to be able to turn off auto-closures on comments. Or maybe even in the configs an array of chars not to close? If nobody else feels this way though, probably not worth the effort. I suppose I am looking for input on this feature.

[isidorn]

We currently have editor.autoClosingBrackets but this does take care of the comments

[alexdima]

@variab1e When commenting out blocks of code, I personally always choose // via Ctrl+/. The reason I do it is that // can comment out block comments and it is cumulative:

    // /**
    //  * Returns the column for the text found at a specific offset inside a rendered dom node
    //  */
    // getColumnOfNodeOffset(lineNumber:number, spanNode:HTMLElement, offset:number): number;

    // // /**
    // //  * Let the line know that decorations might have changed
    // //  */
    // // onModelDecorationsChanged(): void;

I am not sure why you choose to comment block of codes with /**. Why not use /* ?

[Thaina]

I think this is annoying behaviour too

[grolapin]

Me too. Doesn't seem too hard to fix.

[briankendall]

Yup, I am also not thrilled with this would like a way to switch it off.

[dagit]

@alexandrudima You asked why someone would do that?

This came up for me recently as I was trying to find some problematic code. Basically doing bisection search commenting things out. I started by commenting out a huge region of code and then incrementally moving the start of the commented region down the file, but the auto inserted characters were a nuisance.

Definitely a +1 from me on making this configurable.

[ayhanavci]

For me, this behaviour does more harm than good and is pretty annoying.