Skip to content

Conversation

@dmitshur
Copy link
Member

Fixes#49.

This is not tested. Done based on what the email said in #48 (comment), to remove specifying markdown option in the _config.yml.

I don't think we're using any subtle features, so the default markdown engine, whatever it may be, should be okay.

@neelance
Copy link
Member

Yeah. I'm okay with merging and then checking the output.

@dmitshur
Copy link
MemberAuthor

Let's try. Will revert if I spot any issues.

dmitshur added a commit that referenced this pull request Feb 22, 2016
_config.yml: Don't explicitly specify markdown engine.
@dmitshurdmitshur merged commit a323f6d into masterFeb 22, 2016
@dmitshur
Copy link
MemberAuthor

I see some minor differences, but no major issues.

Before:

image

After:

image

The largest minor issue is that code blocks have a strange 0-width left padding.

image

@dmitshurdmitshur deleted the update-markdown-engine branch February 22, 2016 11:50
@dmitshur
Copy link
MemberAuthor

On the plus side, no more warning email!

@dmitshur
Copy link
MemberAuthor

FWIW, the HTML before:

image

And after:

image

@neelance
Copy link
Member

Seems like the CSS file needs an update.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@dmitshur@neelance