Indent/Outdent with tab key does not honor editor.autoIndent=false

[hostilefork]

Issue Type: Bug

When I have:

    /*
     * Comment
     */

If I select it and hit tab, I get:

        /*
        * Comment
        */

If instead I had hit shift-tab, I get:

/*
    * Comment
    */

Same happens with Ctrl-] and Ctrl-[ (if those are supposed to make a difference)

I hoped turning off autoIndent would stop this, but no dice. I also turned off C++ formatting in the JSON config:

{
    "editor.autoIndent": false,
    "editor.detectIndentation": false,
    "C_Cpp.formatting": "Disabled"
}

I have done due diligence by asking (and bountying, +100) a question on StackOverflow to get an answer on what to do about this, but no one seems to know:

https://stackoverflow.com/q/53326134/preserve-spacing-on-indent-or-outdent-with-tab-in-vscode

If someone can provide a resolution here, be sure to go there and get the bounty points.

VS Code version: Code 1.29.1 (bc24f98, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Memory (System)	15.86GB (1.40GB free)
Process Argv
Screen Reader	no
VM	0%

Extensions (3)

Extension	Author (truncated)	Version
vscode-github	Kni	0.30.0
python	ms-	2018.10.1
cpptools	ms-	0.20.1

[wasuaje]

Guys Any update on this?
I'm having the same issue!

[tobia]

Come on, I just tried it in Vim, Sublime, Emacs... no other editor has a bug like this!

For the time being, a workaround is to use the indent-one-space extension, but this should be fixed properly.

[anchann]

This issue also affects indentation of XML severely. For example, with indentation set at 4 spaces, starting with this text:

<Component
 class='something'
 SomeProp='blah'/>

increasing indentation by one step using the "Indent Line" command produces this:

    <Component
    class='something'
    SomeProp='blah'/>

Starting with this text

    <Component
     class='something'
     SomeProp='blah'/>

and decreasing indentation by one step using the "Outdent Line" command produces this:

<Component
    class='something'
    SomeProp='blah'/>

This style of indentation may feel strange to some people, but that's part of the whole issue — who are people, and who is VSCode, to tell others how to format their code? If I wanted my text editor to mangle my formatting, I would opt in to automated formatting.

Increasing and decreasing indentation should be a simple operation of adding or removing one fixed string (in my example, a string consisting of four spaces) to/from the beginning of each line. Yes, there are some important edge cases to take care of (e.g. what happens when one of the selected lines doesn't have enough whitespace to take away on an outdent; or e.g. ignoring the last empty line of a block of lines selection), but VSCode gets them right already (and most plugins that implement things naively do not). Why confound the simple, deterministic operation of changing the indentation level with something as complex (and often buggy, which is why people turn it off) automatic formatting?

If changing the default behaviour of these actions is somehow controversial, can you at least provide "Indent Line Trivially" and "Outdent Line Trivially" pair of actions that people who don't want their code mangled can use?

[heartacker]

hi All, I found that this is caused by the block comments starter word,

just now we can use /** instead of /* or /*! to work around，（but contradicting my coding rule)

#135819 (comment)

and anybody could identify is there anything related to :

vscode/extensions/cpp/language-configuration.json

Lines 1 to 5 in ff1e16e

	{
	"comments": {
	"lineComment": "//",
	"blockComment": ["/*", "*/"]
	},

[heartacker]

👯

[chuckeng]

The work around does not appear to work everywhere:

I think it works for method/function comments, but not comments inside a functions (and who knows where-else).

Also, we have too many lines of code already in that format. So, as a work-around it would allow me to add the *, then adjust indentation, then remove the *. But really that just saves a small bit of time. Usually we work on large sections of code, and we might miss doing this. Once its checked in, good luck changing it without a bug that requires the code to be updated again. :/