On 2010-01-24, at 04:25 , John Gruber wrote: > > On Jan 23, 2010, at 10:20 PM, Caio Chassot <[email protected]> wrote: > >> (Incidentally, this is how I would prefer markdown to work; hear pres?) > > It has never occurred to me that Markdown would be useful in the context of > an email client. What's the idea, that I'd compose in Markdown and the > message would be sent as HTML?
This has been proposed on the list, yes. But that's not what I'm talking about. I'm just talking about Markdown as a text-to-html language in web context, and how GitHub and Stack Overflow changed from "to force <br>, end line with two spaces" to "\n means <br>, period". As in f=f email, \n means \n, but '\n $' means line continuation. It makes some conceptual sense. The original Markdown solution sounds like a hack because you don't want LF to default to line breaks. The f=f solution sounds like, "ok, why would a line ever end in a space? I guess it's just wrapping". Probably too late for that now, unless you want to work on a new Markdown release at this point. Kinda OT for this list too. _______________________________________________ [email protected] mailing list List help: http://lists.ranchero.com/listinfo.cgi/email-init-ranchero.com
