-
Notifications
You must be signed in to change notification settings - Fork 330
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect preview of nested bulleted list #1044
Comments
@yzhang-gh my bad, it was in Bitbucket, not GitHub. I have updated the issue details. |
Bitbucket uses Python-Markdown not CommonMark. Python-Markdown requires "4 spaces" indentation:
Please set the following in your Settings. {
"[markdown]": {
"editor.detectIndentation": false,
"editor.insertSpaces": true,
"editor.tabSize": 4
},
"markdown.extension.list.indentationSize": "inherit"
} |
This should be added as a setting inside the settings UI rather than a manual edit to the settings json file to make it easier on users to find. |
Aren't they present in the Settings (UI)? Or, are you talking about |
The settings weren't showing until I manually added them to the settings.json. Then they showed up. Strange glitch maybe. |
Problem
Nested list indented by three spaces looks fine in the extension preview, but it wraps to one line in Bitbucket README.md.
How to reproduce
README.md
file in Bitbucket:ISSUE: The "Level two" bullets are on the same line as the first "Level one" bullet. It seems Bitbucket requires four spaces to nest lists. According to https://commonmark.org/help/tutorial/10-nestedLists.html you can have as little as two spaces to indicate a nested list, so can we conclude that Bitbucket's MD implementation is non-standard? If this is a case, feel free to close this ticket.
Configuration
Default
Environment
Extension v3.4.0
VS Code
Version: 1.62.1
Commit: f4af3cbf5a99787542e2a30fe1fd37cd644cc31f
Date: 2021-11-05T09:23:14.144Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.1.0
Diagnostic data
N/A
The text was updated successfully, but these errors were encountered: