-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Add option to disable indented code blocs #138
Comments
It's really unlikely that the option to disable indented Commonmark behavior will ever be added. If it's in the spec, it must be supported. But let's see if we can't figure out a solution here. Is there a reason the lists need to be indented by four spaces? Would two spaces work for you? That would "turn off" the indented code blocks. Also, I just tried this as a markdown doc: text = <<~EOS
<ul>
<li>blah blax</li>
<li>blah blax</li>
</ul>
EOS A call to |
Thanks a lot for your prompt answer, @gjtorikian. Actually, I never indent my code with spaces, but with tabs. Furthermore, i found out what simple Could I do something to prevent this? The only way I found out up to now is to remove all indentation. Using fewer spaces is useless since for sub-lists are still needed four spaces of indentation… |
Do you have a sample site I could look into? I might be able to reproduce the problem and implement a fix to minimize the whitespaces. |
Right now I have no website using Commonmark, since it does not generate IDs for headings, and I need them to generate TOCs. As soon as automatic ID generation will be implemented, I will use jekyll-commonmarker for my website and I will ping you by writing here |
I am getting crazy. I have a lot of indented
<ul>
lists, where I need to use HTML since I am adding classes to single lists elements.I write them like this, in markdown files:
and they are parsed like this:
I can’t therefore indent anything, not even in
div
s or inol
s, since they are parsed as codeblocks.I would really love the capability of disabling this.
Thanks a lot in advance!
The text was updated successfully, but these errors were encountered: