Vscode-markdown: Tab indentation is disabled

[mumeiyamibito]

What is the problem?

I wrote markdown document for converting pandoc.
My indent settings is set to "Indent using Tabs".
When pressing tab key for writing ordered or unordered lists, double or triple spaces were inserted before list (double spaces for unordered list and triple spaces for ordered list).

How can I reproduce it?

My environment is VSCode Ver. 1.29.1 on Linux Mint 19 Cinnamon edition (64bit).

1. Initialize VSCode ($HOME/.vscode and $HOME/.config/Code are removed).
2. Launch VSCode.
3. Create and save a new markdown document.
4. Set to "Indent using tabs" of indent setting by clicking status bar.
5. Write ordered and unordered lists (Each list has two lists).
6. Press tab key on a child list and confirm of indentation by tab (In this time, I confirmed that the indent is tab).
7. Install Markdown All in One.
8. Reload VSCode to enable the extension.
9. Confirm status for indentation by repeating procedure 3 to 6 (The issue was occured).

Is there any error message in the console?

No.

[yzhang-gh]

Thank you. The indentation behaviour is changed in v1.8.0. I will make it be aware of the "indent with tabs" setting later.

For a workaround, you can pause the extension auto update and then install a previous build from here.

(Maybe you need to uninstall v1.8.0 first rather than directly override it with v1.7.0)

[garyking]

Probably related: My indent settings are spaces: 4, and yet this update makes tab-indents only indent 2 spaces. So it is just ignoring indent settings completely.

Also, VSC 1.3 released a few hours ago has a new feature that allows you to specify what extension version you want installed, so you can now easily freeze this extension to v1.70.

[werunom]

I also have reverted to the previous version of the extension :(

Also, with this new change, how tab functions depends on what precedes the cursor. For instance, If the cursor is just after + (unorder list symbol), then it moves 2 spaces. However, in other places, it respects 4 spaces. This can be very disorienting for certain users. (Not to mention the non-uniform presence/absence of indentation guides in my documents.)

@neilsustc - I understand that there has been a good amount of discussion that has gone into this new change regarding indentation. But I feel this could have been provided as an option in the settings.

I think providing the following option in extension settings might keep everyone happy:

1. if users want, they can keep tab-indentation to work according to their vscode general settings (inserting tab or 4 or 2 spaces depending on the vscode configuration). this would mean that the general setting of tab will dictate how indentation everywhere should work.
2. Alternatively, there can be an option to override the above setting and make markdown files use lints (like markdownlint or prettier) prescribed tab indentation.

Just one way of resolving the confusion. There might be better workarounds ...

[yzhang-gh]

I definitely agree with you. Will work on it during the weekend.

[yzhang-gh]

Could you please test on the dev build? There is a new option

[mumeiyamibito]

@neilsustc
Thank you for fixing it.
In the above my procedure, I confirmed that indentation normally worked with inherit setting.

[werunom]

@neilsustc --- dont mind me asking, but when are you planning to release this fix? :)

[yzhang-gh]

😅 Thank you for asking. We are now working on a performance issue (#360). Will surely have a new version this weekend.

[yzhang-gh]

Shiped with v2.0.0