Seems nothing here.
16 |```, or are indented with four spaces. I recommend only using the fenced code blocks -- they're easier and only they support syntax highlighting.
198 |
199 | ```javascript
200 | var s = "JavaScript syntax highlighting";
201 | alert(s);
202 | ```
203 |
204 | ```python
205 | s = "Python syntax highlighting"
206 | print s
207 | ```
208 |
209 | ```
210 | No language indicated, so no syntax highlighting.
211 | But let's throw in a <b>tag</b>.
212 | ```
213 |
214 |
215 |
216 |
217 | ```javascript
218 | var s = "JavaScript syntax highlighting";
219 | alert(s);
220 | ```
221 |
222 | ```python
223 | s = "Python syntax highlighting"
224 | print s
225 | ```
226 |
227 | ```
228 | No language indicated, so no syntax highlighting in Markdown Here (varies on Github).
229 | But let's throw in a tag.
230 | ```
231 |
232 |
233 |
234 |
235 | ## Tables
236 |
237 | Tables aren't part of the core Markdown spec, but they are part of GFM and *Markdown Here* supports them. They are an easy way of adding tables to your email -- a task that would otherwise require copy-pasting from another application.
238 |
239 | ```no-highlight
240 | Colons can be used to align columns.
241 |
242 | | Tables | Are | Cool |
243 | | ------------- |:-------------:| -----:|
244 | | col 3 is | right-aligned | $1600 |
245 | | col 2 is | centered | $12 |
246 | | zebra stripes | are neat | $1 |
247 |
248 | There must be at least 3 dashes separating each header cell.
249 | The outer pipes (|) are optional, and you don't need to make the
250 | raw Markdown line up prettily. You can also use inline Markdown.
251 |
252 | Markdown | Less | Pretty
253 | --- | --- | ---
254 | *Still* | `renders` | **nicely**
255 | 1 | 2 | 3
256 | ```
257 |
258 | Colons can be used to align columns.
259 |
260 | | Tables | Are | Cool |
261 | | ------------- |:-------------:| -----:|
262 | | col 3 is | right-aligned | $1600 |
263 | | col 2 is | centered | $12 |
264 | | zebra stripes | are neat | $1 |
265 |
266 | There must be at least 3 dashes separating each header cell. The outer pipes (|) are optional, and you don't need to make the raw Markdown line up prettily. You can also use inline Markdown.
267 |
268 | Markdown | Less | Pretty
269 | --- | --- | ---
270 | *Still* | `renders` | **nicely**
271 | 1 | 2 | 3
272 |
273 |
274 |
275 | ## Blockquotes
276 |
277 | ```no-highlight
278 | > Blockquotes are very handy in email to emulate reply text.
279 | > This line is part of the same quote.
280 |
281 | Quote break.
282 |
283 | > This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
284 | ```
285 |
286 | > Blockquotes are very handy in email to emulate reply text.
287 | > This line is part of the same quote.
288 |
289 | Quote break.
290 |
291 | > This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can *put* **Markdown** into a blockquote.
292 |
293 |
294 |
295 | ## Inline HTML
296 |
297 | You can also use raw HTML in your Markdown, and it'll mostly work pretty well.
298 |
299 | ```no-highlight
300 |
387 | ```
388 |
389 | Or, in pure Markdown, but losing the image sizing and border:
390 |
391 | ```no-highlight
392 | [](http://www.youtube.com/watch?v=YOUTUBE_VIDEO_ID_HERE)
393 | ```
394 |
395 | Referencing a bug by #bugID in your git commit links it to the slip. For example #1.
396 |
--------------------------------------------------------------------------------