I had gotten this to function a bit better, and certainly seems it has to do with how I am writting this out. I think the root of the problem was how I had the start of the number list right up next to another item, as you can see in the image, I added a return after the "summary of changes". Do still have to figure out how to revisit the number list since it tries to take #4 and wrap it as a bullet list inline.
nick closed this discussion
on 13 Feb, 2020 04:50 PM.
Brett re-opened this discussion
on 13 Feb, 2020 08:54 PM
Brett on 13 Feb, 2020 08:54 PM
If in doubt, always add whitespace around block items like code, lists, blockquotes, etc. Also, it appears you're actually trying to make sub-lists with the unordered lists, but they're not indented (unless something got shifted in the paste). They should be indented 4 spaces to function correctly and not break the rest of the list.
Looking at it I have to assume it lost formatting, though, as the line server1 server.xml looks like it should have been a code block? In which case it would need to indent 8 spaces. Oh, and that will be another source of confusion, Marked prefers 4 spaces for list indentation whereas github will let you get away with 2. Using 4 will work in both places, though.
Thanks Brett - I feel bad how there are likely times you are fielding markdown newbie questions as opposed to product related issues. Both your points are keys to getting this to work. I also had a line "header if you will" without a return directly before the number list which seemed to affect the rest of the series down stream. Then additional indentation is what had everything looking as I expected. The image was my working result.
This has been great in the few hours I've been working with Marked. I write everything in VIM and Marked has added a nice visual touch with many wonderful features. Sorry for the noise!