Currently if you start a line with > to indicate a block quote, add some text, then hit return, Drafts doesn’t automatically insert another > at the beginning of the new line. This feels wrong given the original Markdown spec, which states that each new line in a block quote should begin with > .
I’m wondering if Drafts shouldn’t treat block quotes similar to lists, inserting the > (similar to * , 2. , etc.) automatically, and then automatically removing it if you hit return again without typing any text.
I don’t have any strong opinion about it. No one has asked for this before, but seems reasonable. Looks like it varies how it’s implemented across editors - of the four other popular editors I just tried, two did quote continuation like you describe - the other two did not. So I guess there’s not a clear consensus.
yes thats right, personally I’d agree that it would automatically insert the indicators, because they dont annoy me and i dont need to scan all the lines above to check out if this is a quote now or not.
Thanks for the reply. Out of curiosity, which two didn’t automatically insert > after a hard return? I’m moving away from Bear (which did) to Ulysses (which also does).