MD improvements, client side warnings

[bjb568]

Please test to make sure it works.

[thomas-daniels]

Error message, not sure if related to this:

/home/programfox/DevDoodle/node_modules/mongodb/lib/utils.js:97
    process.nextTick(function() { throw err; });
                                        ^
Error
    at Object. (/home/programfox/DevDoodle/node_modules/mongodb/node_modules/mongodb-core/lib/error.js:42:24)
    at Module._compile (module.js:462:26)
    at Object.Module._extensions..js (module.js:480:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:367:17)
    at require (module.js:386:17)
    at Object. (/home/programfox/DevDoodle/node_modules/mongodb/node_modules/mongodb-core/index.js:2:17)
    at Module._compile (module.js:462:26)
    at Object.Module._extensions..js (module.js:480:10)

[minitech]

Unclosed quotation marks still result in <q>; I don’t know whether that’s intentional.

"test

<q>test</q>

[bjb568]

@ProgramFOX Huh… maybe try updating mongodb? I think there's a new version.

[bjb568]

@minitech Yes, that's intentional, all formatting characters must be escaped outside of code and samp.

[thomas-daniels]

Eh, that explains it, I didn't start the MongoDB server...

[thomas-daniels]

***test*** says "illegal nesting of *", but it is valid: expected result = bold + italic

[bjb568]

That's bad. I'm not sure how it should parse that. ***test *test** and ***test **test* require a different order of <em> and <strong> so it's not trivial to parse.

I'm wondering if we need to support it at all, since it could be abused to shout and two levels of emphasis are enough for most cases…

[minitech]

Why not from 3 to 1?

[bjb568]

I suppose 3 to 1 would work.