On 14 Nov 2014, 5:47 am, Ann Amber wrote:
Wow… my post above looks completely different that the way I carefully spaced it before posting, so it was easily readible like the others.
Don’t know why it did’t hold.
I saw your message in Mail, and it looked as you intended, but as a long-term user of Markdown (which is how this list is formatted on the Web) I could see an uh-oh coming.
If you post from the Web to the list, there is a live-preview to show you what it will look like when published (the preview actually loops through the same formatter that the site uses when showing messages). Markdown was designed to mimic the sorts of formatting you may be accustomed to using in plain-text mail messages to indicate structure and emphasis. If you’re not familiar with Markdown, here’s a quick primer:
###Paragraphs
Separated from one another (and from other block elements like lists or pre boxes) by two returns.
###Lists
Separated from other content by at least two returns, and then each line started with one of the following: a single asterisk, followed by a space, followed by your list item text, or started by a numeral (any number will work, they will always come out as 1,2,3) and a space to make an ordered list. You may not mix numbers and asterisks within a single list, unless you indent the numbers by four spaces.
###Headlines
Begun with one through six octothorps, an optional space, and your content.
### H3 tag here
###Code Blocks and Phrases
These come in several flavors. Which to choose depends on your content.
For a single word or short phrase in a sentence, use a single back-tick (`) on either side of the word or words.
For a block of code, like a function definition or a brief example of HTML, indent each line with at least four spaces. (My example of the H3 above was done in this manner.) (Everything over 4 will be formatted as typed, so as long as you indent with spaces, you will get what you expect. If you post by e-mail, and use tabs for formatting, the system will translate each tab into four spaces for you.
For a more complex block of code, or any code with more than about 40 characters to a line, use a “fenced” code block. All by itself on one line, type four tildes in a row (~~~~) followed by a return, then your code, then another four tildes on their own line. Then two returns before you start another block of text.
###Gist and Pastie
For more involved (larger, heavily formatted, need color-coding to understand) examples, use either https://gist.github.com or http://pastie.org to create a “paste” of your code. Either of those services will redirect you to a page showing your code neatly formatted based on the language in use. Copy the URL for that page, and paste it all by itself on a line in your message. The formatter will convert that URL into an injected block, leveraging all the power of those platforms’ display engines.
https://gist.github.com/walterdavis/35b6de857e9f14fcf145
Walter
tutorials mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options