similar to: putting markdown into the browsers

brett terpstra continues his obsession with markdown... > http://fuckyeahmarkdown.com/ there's also a g-rated version: > http://heckyesmarkdown.com/ brett has accomplished more in the last three months than this listserve accomplished in the last three years. and it looks like he's only just getting started... meanwhile, fletcher is about to send off his rocket, which

spring has sprung, so on this day of grass, i guess i just can't hold this back any more. > http://zenmagiclove.com/aarp2.py voila. a dingus for zen markup language. lighter than markdown. _and_ more powerful... i know. wha? go figure. not that it's a competition. supporters will love finally seeing a look. detractors will love the bugs i left in there, just for them, as

While I empathize with your predicament, I generally prefer not to have expletives in my inbox. Also, what has this to do with markdown? On Jul 5, 2013 7:20 PM, "bowerbird" <bowerbird at aol.com> wrote: > fan_fucking_tastic. > > somebody hit another one of the dead skunks on this road. > > -bowerbird > > _______________________________________________ >

so much for the markdown listserve grapevine... it ends up that there has been a markdown-savvy display-in-real-time app for a couple months now, by the name of "macchiato", coded by a college kid. > http://getmacchiato.com > http://kswizz.com/post/8624456381/macchiato > http://mac.onedayoneapp.com/macchiato/ > http://shawnblanc.net/2011/08/macchiato/ >

i should probably just let this listserve die, but... *** anyway, it's that brett terpstra fellow again... > http://brettterpstra.com/my-ultimate-markdown-editor-wishlist/ -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20120508/8915e1cf/attachment.htm>

i am considering writing converters between my "zen markup language' and "markdown", but i don't know which version of markdown to target. i'd think it'd be the "pandoc" version, and i understand that to be closest to "multimarkdown", but gruber has said he "disagrees" with "almost every part" of multimarkdown's syntax

fletcher said: > For any consensus to come about, > I think we need to agree on the > fundamental purpose and philosophy of > the consensus we claim to be interested in. it would be nice. > Otherwise many of these discussions will > continue to occur without much hope of > moving forward to any actual outcome/resolution. yep. > it's

where are the worthwhile markdown dingi? (dinguses?) i'm interested in any dingus that can take a "reasonable" amount of text -- let's say anything up to a megabyte -- and return the results in real-time, without a long wait... ideally it'd handle something more than gruber-minimum, and an a.p.i. (that'd take a u.r.i. as input) would be dandy... bonus points for

alan said: > I think I am in agreement, > if by "isn't necessary" you mean to say that > simply providing more features to Markdown > doesn't force end users to use them, > or even really know they exist. except that wasn't what i meant. i mean that it's not necessary to trade simplicity in order to get the power of additional

like history, the future is decided by the people who write it... > http://www.codinghorror.com/blog/2012/10/the-future-of-markdown.html by the way, if you want a form of light-markup which is still flexible enough to be molded, but will be _totally_ free of ambiguities and "edge-cases", and governed by a well-written specification and thorough documentation, along with an

a specification will _eventually_ be used, by someone, to tell the user they are doing things "wrong", won't it? and doesn't that turn markdown's genesis upside-down? heck, next thing you know we'll be telling them to r.t.f.m. i would prefer that implementers get more sophisticated about teasing out the user's intent in "ambiguous" cases. of course,

i've released the first beta of my e-book converter-tool. you are invited to throw stones at it (and at me) if you like: > http://jaguarps.com "beta" is a compromise. i developed it on a mac, so that particular version is solid. but "alpha" would be a better label for the status of the windows and linux versions, so if you have one of _those_ machines, and you

godspeed, steve. thanks for giving us the tools to catch fish. -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20111006/3e1c11bd/attachment.htm>

hello, i am looking for advice regarding the best repo from which to download "markdown" for use on a mac. on my ubuntu machine i just installed some standard markdown package with apt-get. but i have not found anything equivalent for my mac machine. i am looking for a maintained package from a reputable repo site that can be automatically installed and upgraded using the packaging

> The use of? monospace fonts > is an expectation for reading Markdown. > Really, it's the whole point. um... no. going way back to "triumph of the nerds", the number-one example steve jobs used to symbolize the absence of any esthetics at microsoft (and thus -- by extension -- inside the head of bill gates) was the fact they found a monospaced font acceptable.

Not only is [Markdown] dead, it's starting to smell really bad. (Apologies to Pike.) It's author appears to have little interest in developing the tool and participating in the community which uses it. I'd like to see the community cooperate toward a specification which addresses the shortcomings and ambiguities of Markdown (even if it need be released under a new name).

ok, i waited for 2 weeks, and still no votes -- none! -- on whether my posts are sufficiently on-topic, or not... and that basically confirms what i suspected all along, which is that no one really cares one way or the other. even the guys who put up the bitchy posts are probably just having a bad day, and they don't have a dog to kick, and the wife made 'em stop smoking herb, so they

i'll be doing some experiments myself, but i thought i'd ask here first about back-translation and round-tripping with markdown and its xhtml output. the object is to take markdown output, reduce it back to a markdown text-file, then regenerate the output again and compare it with the "original" output, repeating if necessary until there exists a pair of files that give perfect

jquery table editor in .html: > http://warpech.github.com/jquery-handsontable/index.htm -bowerbird -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://six.pairlist.net/pipermail/markdown-discuss/attachments/20120801/7488fd1d/attachment.html>

So, hi all. First time commenting on the list. I personally think having tags (whether of type "author:" or type "by") is useful for two reasons. One: It allows multiple tags to be entered. Two, it clears up the potential problem listed by Fletcher regarding tags. by Christoph Freitag Affiliation: XYZ by Fletcher T. Penney Affiliation: ABC tags: Markdown, Standardization,