tag:support.markedapp.com,2011-09-11:/discussions/problems/156783-markdownMarked: Discussion 2020-02-13T21:22:49Ztag:support.markedapp.com,2011-09-11:Comment/480872882020-02-13T16:19:43Z2020-02-13T16:27:05ZMarkdown Formatting<div><p>I am curious about markdown formatting behavior I am seeing while using Marked but it doesn't seem to render the same if/when I upload the file to github. Below is what I have in my document and i attached an image of what it looks like in Marked (img1) and then what i see in github (img2). Let me know if i am doing something wrong, if this is unsupported, or other. Thanks.</p>
<pre>
<code> 1. Change bridge connections from 30 to 60
- Required object spawner restart
2. Update metadata SASApp Stored Process Server Load Balancing options
- Maximum Cost = 500
- Start size = 60
3. server.xml changes
server1 server.xml
- maxThreads = 1024 (no change)
- acceptCount = 100</code>
</pre></div>nicktag:support.markedapp.com,2011-09-11:Comment/480872882020-02-13T16:48:43Z2020-02-13T16:48:43ZMarkdown Formatting<div><p>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.</p></div>nicktag:support.markedapp.com,2011-09-11:Comment/480872882020-02-13T20:54:45Z2020-02-13T20:54:45ZMarkdown Formatting<div><p>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.</p>
<p>Looking at it I have to assume it lost formatting, though, as the line <code>server1 server.xml</code> 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.</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/480872882020-02-13T21:03:25Z2020-02-13T21:04:38ZMarkdown Formatting<div><p>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.</p>
<p>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!</p></div>nicktag:support.markedapp.com,2011-09-11:Comment/480872882020-02-13T21:22:46Z2020-02-13T21:22:46ZMarkdown Formatting<div><p>Yeah, that looks much better!</p>
<p>I'd say that 80% of my customer support is correcting people's Markdown, but it's no sweat :). Glad to hear Marked is proving useful!</p></div>Brett