The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I had the source on green stripy paper. A friend and I wrote a customised version of it (in FORTRAN 4) to run on our college computer (a Pr1me 300B) with our own messages and map. Nobody liked it much so we gave up and I wrote a version of the early Star Trek type game instead which proved immensely popular - so much so that we were instructed to restrict access to it as all terminals were permanently occupied with students playing it.
- I would love to change the world, but they won’t give me the source code.
It annoys me enough in QA, and I have it disabled there! Even disabled, it manages to creep in and add code blocks, strike throughs, and such like stupidity to code. Fortunately, it's only there until I refresh a solution, but ...
Sent from my Amstrad PC 1640 Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
I just dug through a work request that was in part fixing a boatload of markdown documents so that code blocks in the middle of lists were formatted correctly. Gotta make sure all our text lines up nicely...
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I like Markdown in general, but dislike the case you ran into: there are so many Markdown implementations that *mostly* work the same way, but you run into edge cases like the line break where it's inconsistent across implementations - some do it one way, others do it another way, and others don't support it at all.
Interestingly, the documentation you linked to is from Commonmark - which is an attempt to standard Markdown and give all implementations a common spec to target.
Maybe we should give Bitbucket a hard time for using a substandard Markdown parser.