similar to: fried fish, available, for free

here's a little present for y'all... > http://jaguarps.com/tools/jaguar-editor-727.png that's a screenshot of my latest project... i've slapped a little text-editor in front of my e-book conversion routines, so that the feedback loop becomes much tighter, goosing the learning process considerably. no more mystery about whether it's right; if it looks correct in the

I am using indefero,and its wiki use markdown as wiki syntax,and I found that markdown do not support Strikethrough ? Thanks!

Gentlefolk, I have been thinking on Markdown's lack of "proper" table support for a long while now. Here's where I have arrived... ## I Don't Like HTML Tables It is often argued that embedded HTML is the way to markdown rich tables. Unfortunately, this contradicts the higher markdown ideal that a raw markdown document (including tables!) should be good 1. Firstly for

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>

Hi, I'm writing a Markdown Parser in Scheme by porting bits of Markdown.pl. As you're probably aware, the Perl version massages the file into the final output with a number of regexes. In my version I'm trying to use the regexes to detect the starts and ends of the features and then take specific action to emit the final representation. I'm doing it this way because I want to

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 > > _______________________________________________ >

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

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

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

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>

seumas said: > What confuses me is what > this all has to do with markdown. david said: > I find discussion of techniques for > building Markdown parsers very interesting. i can justify myself. indeed, it's a good exercise every so often, just to ensure that your position and directionality are focused. but it's not right, or fair, that every month, someone

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).

sherwood said: > If agreement is reached, then the group > looks at variants 6,7,8,9 and inquires > if they would like to join in this effort. well, that kind of leveraged consensus would have been the way to go about this process a year ago. but not today. > Has anyone collected a would-be canonical list > of either the ambiguous cases in original MD, >

looks like my message from last week about writing tools was right on time... we are enjoying a display of fireworks now going off in this particular arena... fletcher started work on an editing app with markdown-preview built right in, after reporting on his blog that he had "seen the future" in ali's post last month, where ali debuted his syntax highlighter, and fletcher is

Dear readers, of the Markdown-(Extra)-Discussion list. After including Markdown as the Markup language of choice for my configuration files I stumbled over a feature I was missing: Adding e-mail links with names. I came up with a little hack I want to share with you. Old Syntax: (mailto:$mailadress@$mailhost) New Syntax: (mailto:$mailadress@$mailhost[ My Name) changes: 1) function

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/ >

this is fascinating: > http://daringfireball.net/linked/2011/08/05/markdown-uti i don't know (and don't care about) any possible significance of such a pronouncement on a "uniform type indicator", but i think that it's interesting that gruber has decided to make _any_ type of statement on markdown, with the big moves now underfoot, and doubly so when he chooses to

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,

my take on a table specification. it's short. this is for my own system, so if some of it doesn't seem to apply to you, that's why... *** first, the overview: keep it simple, stupid. if your table is too big or too complex to grok on an iphone, then it's too big or too complex. so break it up, into a series of smaller tables. and when you do so, do it in a way such that

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