Lists directly below headings do not render as lists

[travs]

Hey Elliot, have had an issue raised over on markdown-pdf, where this markdown does not render as the preview pane does.

Not sure if having a list directly below a heading is valid md or not, but just raising this issue here since it seems mdpdf does not treat it as such.

All the best!

[elliotblackburn]

Hey there @travs, I'll take a look at the markdown spec and see. In my experience a lot of systems require a new line between a header and a list for it to render correctly, but that doesn't mean it's not a bug.

I'll take a look at the various markdown specs around (though as we know, they're all a bit thin) and get back to you via this issue.

Just an off-topic note, I'm currently working on replacing the pdf rendering engine, it's currently a PhantomJS based one and I'll be moving it over to Puppeteer. This shouldn't effect much but I'll get in touch with you when it's nearly done for a round of testing if you wish to update markdown-pdf to that version when it's out.

[travs]

@BlueHatbRit Awesome, and thanks for the heads-up. I would definitely want to support your new version as well, and having it in markdown-pdf would be great battle testing. Feel free to raise an issue in the atom package repo or message me on keybase when it's ready!

[elliotblackburn]

Just had a look at this issue again using Showdown directly. To achieve what the user is attempting, they probably want this markdown. This may not be what GFM requires, but it's what Showdown's flavour requires at the moment, so to achieve the effect they will need the following:

# This is an example of what I'm talking about

- ## I like to make outlines like this

- ### I make section headings like this
  
    - This shows up as anticipated in preview  
    - but exporting via markdown-pdf results with either no results or with hash marks preceding the section heading text instead of matching the preview.

- There are also funky spaces with some of the letters, but I think someone has documented this already. 

We've already got discussion in another thread about the possibilities of supporting other markdown flavours. I'm going to open an issue soon to look at implementing another markdown -> html engine to support GFM and potentially CommonMark so people have options. Once I've opened that, I'll close this issue as technically it's not a bug at the moment.