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
autoindent problem inside GFM fenced code block #78
Comments
Vim Markdown does support fenced code blocks by default. To make sure I understand. Setup:
Action: Expected:
Observed:
(4 spaces). If that is what you mean, then its a difficult decision what is the best behavior. When writing markdown code in markdown code, observed is the desired behavior. What do you usually want to put in the code block (which programming language?) that often starts in hyphens |
Hi, thanks for responding. I understand that the autoindent might be desired when writing markdown code.
this is no longer markdown code. It's raw text which should be unformatted. The text I'm writing is just a bunch of text notes - not a programming language. It could, for example be unix command output which I've annotated in some way. I can understand if it's difficult for the plugin to detect if the user is in a fenced section or not - you'd have to match up pairs of fences. But if it can detect this then I would say it shouldn't interfere with the auto-indentation in a fenced section - it should not make any assumptions about the format of the raw text which is about to be entered. Having said all of that, I've just been giving my vim config an over-hall and that behaviour seems to have gone away. Perhaps my Vundle has picked up a later version in which this behaviour has changed ? |
Weird, I still reproduce on master. |
Hi, I don't know if you intend to support Git Flavoured Markdown or not. If so I've noticed a problem inside fenced code blocks.
For example, enter the following:
Then press o to add a line below the last line and it will try to autoindent.
The text was updated successfully, but these errors were encountered: