dean allen is gone

dean allen slipped the bonds last week. allen was one of the pioneers of light-markup, in the form of his 2002 entry "textile", which he billed as "a humane web-text generator" that would enable a person to "simply write". lots of people took part in the invention, yes, but if you had to

an interesting throwaway line

gruber posted about markdown on his daringfireball blog, which is rare enough to be noticeable. but it became fully remarkable when its final sentence made a passing reference to a possible "update to markdown" event -- as if such a revision isn't a thing he's always steadfastly refused. this

re: Feed.TXT - A Free Feeds Format in Plain Text w/ Structured Meta Data and Markdown ;-)

gerald said: > May I highlight the latest (and greatest) feed format aaron swartz in 2002 said: > http://www.aaronsw.com/2002/rss30 -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net

beaker-browser supports light-markup sites

beaker-browser is an interesting experiment. and it's one of the pioneers of something that i suggested some time ago here, that the web should support light-markup in a native way, by allowing people to simply mount such files, which are then auto-converted by the browser. >

re: markdown rules / recommendations

gerald said: > If you know another see what the brett terpstra says: > http://brettterpstra.com/2015/08/24/write-better-markdown/ -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net

re: New Static Site Theme for World (Literature) Classics in Markdown e.g. A Tale of Two Cities, The Trial, etc.

gerald- congratulations on the new wrinkle... *** speaking of meet-ups > http://viennahtml.github.io congratulations to kramdown for being selected the github-approved converter. which means it'd sure be nice to have a javascript implementation of kramdown. because i can now

organizational bloat

you can pretty much tell how much organizational bloat a company has by the complexity of its url structure > > https://developer.apple.com/library/prerelease/mac/documentation/Xcode/Reference/xcode_markup_formatting_ref/index.html#//apple_ref/doc/uid/TP40016497 -bowerbird

re: markdown wiki for compiling documentation

alan said: > take a look at the much-respected Pandoc project. good suggestion. and along those lines, perhaps go all the way, and use a wiki app coded by pandoc's john macfarlane. > https://github.com/jgm/gitit a running demo, with a sandbox, is at: >

commonmark is used in the swift compiler

> https://swift.org/source-code/#cloned-repositories > The source code for CommonMark, > which is used in the Swift compiler. > https://github.com/apple/swift-cmark ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net

crowd-sourcing for a new javascript browser-based prose editor

marijn haverbeke said: Sometimes I lie awake at night, feverishly searching for new ways to load myself down with more poorly-paying responsibilities. And then it comes to me: I should start another open-source project! http://marijnhaverbeke.nl/blog/prosemirror.html

re: does fireball markdown support anchor links?

aristotle, your mockery entertains me immensely. -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

markua -- a new flavor for long-form documents

some of you probably know that leanpub.com has been creating a new flavor targeted at books, which they are calling markua. their in-progress documentation: https://github.com/markuadoc/markua here's a little javascript thing to pull all of the chapters together:

re: does fireball markdown support anchor links?

david said: an option, though not a pretty one. it's ugly, yes, but that's not the worst part. the worst part is that it is a lot of work -- especially if you want a table of contents. and then it's obstacle-clutter while editing. it's really something that should be handled by the

that's an endorsement

interesting to see asciidoctor.org has this quote from linus torvalds... Use AsciiDoc for document markup. Really. It's actually readable by humans, easier to parse and way more flexible than XML. — Linus Torvalds -bowerbird ___

re: people are doing interesting stuff (more)

http://jbt.github.io/markdown-editor/#HY+xcsQwCER7f8V2aZIr8kfIwhZzEngEOc/9fdB1sMPuPkgrGk/+crgNNmXczXKra1xSNNETLkM6zW9gM+1vSKCKX53eDlGXyiD8/lyUrkHzWe1WcJWw+di2vBbHNa1QSbPach+H7H89EAYZdEo6m93IPs+WIWcLFN4TIaN3652KTQp58Sd4UbG+ZJoO1lhk1Atn1ecJiZZRjJiUUjSKxdz5iKxf6s7+2P4B and here's someone who's

kudos and major props

david said: I made something similar a few years ago yes, you did indeed. and i remember now thinking back then that it was brilliant. you even anticipated the url-too-long problem by using bitly, as well as combining several hashify into a single longer one. and this reminds me that other

markdown in a medium editor clone

markdown in a medium editor clone: http://ionicabizau.github.io/medium-editor-markdown/ -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

pandoc fully exposed online

finally... https://github.com/osener/markup.rocks -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

re: Awesome Books (in Markdown)

gerald said: Again thanks for the great comments. sure thing. thanks for creating the resource. one thing i forgot. the most interesting thing about project gutenberg these days comes not from that project itself, but from an effort that calls itself project gitenberg, which is putting the

re: never to late

i said: hey, it's never to late to muddy the waters! see? if this listserve were stored in github, i could correct that error to never too late. thank goodness for github... -bowerbird ___ Markdown-Discuss mailing list

re: Awesome Books (in Markdown)

gerald said: the idea is to have the source AND the rendered book in hypertext aha! great point. i see the utility now... For Project Gutenberg you get the source (but not a rendered book) which is where i entered this thread... :+) as, indeed, for some time, p.g. has offered

re: Awesome Books (in Markdown)

gerald- gosh, i think that's the second time i've called you gerard, instead of _gerald._ my apologies, again! -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

re: Awesome Books (in Markdown)

gerard said: Might be great to get some classics (in the public domain) e.g. Shakespeare, Dickens and friends. your other page, gerard, gave a nod to other forms of light-markup, including restructured-text, asciidoc, textile, etc. so i'm unclear if this page now means markdown in the

js syntax highlighting for markdown (not for codeblocks in markdown)

honest question: why specifically is it that you would like syntax highlighting? i can imagine benefits, but am uncertain exactly which one(s) you're looking for. the reason i ask is that i believe that it might be possible to get what you want via easier means. but i'm just not sure what it is

fiddle.md

i keep thinking everyone has seen sites like this: http://fiddle.md but then yet another one pops up, and a new group of people say this is such a good idea! https://news.ycombinator.com/item?id=9262260 contrary to its claim, fiddle.md isn't collaborative, and isn't even particularly

wrapping it around

i thought when i made z.m.l. that we were at the very end. now, though, the new york times has wrapped it back around with the debut of archieml, or aml. i worry that this means we are destined to go through the entire alphabet again? -bowerbird p.s. i appreciate how the times has agreed

re: serving markdown directly : any suggestions?

converting light-markup to .html ain't rocket-science. really. you can use any language to do it. specifically including perl. and besides, i think it's kinda cute that some perl people would look down on php, ruby, and python. good for the gander, eh? but if i had to place a bet, it

mou makes its funding goal for a 1.0 release

mou, as you may know, is a markdown editor. with its second $5,000 company sponsorship, mou has reached it's $20,000 indigogo goal... albeit, the effort engendered some resistance: http://weblog.masukomi.org/2014/10/09/why-i-wont-be-backing-mous-crowdfunding-campaign the big thorn is that,

re:

virgil said: Is there any way that the developers can come together on this very small part of the Markdown world? i'd have to say it looks like your answer is no, virgil. if it's any consolation, it's not you; it's always like this. have a nice weekend. have a nice november. have a

re: Using fragment identifiers with Markdown docs

sean said: It is useful to say things like readme.md#how-to-install So that a Markdown editor could scroll to the right content. yes. indeed, that's a useful feature in many contexts, including ones where no such id exists in the .html. see:

re: let us not discuss that here

i sent jakov a reply backchannel. take it all backchannel please. here's a post i made elsewhere, but i think it's relevant here too, in case anyone has any feedback. - call me crazy if you like, i don't mind, but... there's no need

re: let us not discuss that here

i got a chuckle out of the fact that jeff atwood instructed me that i was not allowed to point to the beyond markdown series on medium.com, on the commonmark forum and then proceeded to _delete_my_comment_where_i_had_given_a_link._ i considered my comment to be an on-topic reply to an on-topic

re: let us not discuss that here

oh, crap, i forgot to mention that beyond markdown -- part 4 is now available for your perusal. ;+) https://medium.com/@bbirdiman/beyond-markdown-part-4-9b4dc6841d7e if you'd like to discuss anything, send me an e-mail. thank you. -bowerbird p.s. and if you know jeff atwood, feel

money for mou

interesting to see if there is any demand: https://www.indiegogo.com/projects/mou-1-0-markdown-editor-on-os-x-for-you -bowerbird ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net

let us not discuss that here

ubi said: shouldn't this be moved to some other mailing list? i sent only one notification, of the series, and that was because i did not want to be seen as dissing markdown without giving a fair notice. and, for the record, i'm _not_ dissing markdown. i'm doing what john gruber has always

september is still the cruelest month

maybe perhaps it's time to go beyond markdown. i don't want to talk about you behind your back... and do please let me know if i get anything wrong! https://medium.com/@bbirdiman/beyond-markdown-part-1-2300665659f7 https://medium.com/@bbirdiman/beyond-markdown-part-2-b3527d2b9dcf

clarification of terms would be a good thing

fletcher said: this is NOT Markdown when you do this. thanks for your guidance on this, fletcher. today's world seems to be confused about what markdown _is_ and what it is _not._ perhaps a good explanation would be useful? you know, one that defined markdown explicitly, so we knew what it

big companies and bloated code

so i'm finishing up my latest example of a working light-markup system, and it's running under 45k at the moment. i thought i'd include embedding in it; you know, the typical stuff from youtube, and twitter, vimeo, vine, instagram, etc. my word. embedding from these big companies involves some

re: wysiwyg and light-markup are oil and water

mofo said: I think a mark down wysiwyg would still be very useful, even if not perfect except it wouldn't be anywhere near perfect. i'm saying that it is, in the end, _unworkable._ Take for instance Adobe dreamweaver. It can edit both in output mode and in source code. except

re: wysiwyg and light-markup are oil and water

mofo said: Yea, but I want to see more of the actual output rather than the markdown representation. But I don't want to lose track of what parts of the output can be seen in the now 'smaller' input i'm not following you. but i'm sure it's just a simple matter of terminology. when

the basic gruber markdown basics

# THE GIST OF MARKDOWN'S FORMATTING SYNTAX ### an adaption from text by John Gruber http://daringfireball.net/projects/markdown/basics ## PARAGRAPHS A paragraph is simply one or more consecutive lines of text, separated by one or more blank lines. Normal paragraphs should not be

wysiwyg and light-markup are oil and water

there is a lot of surface appeal to a system which combines wysiwyg and light-markup. and one can do a few simple combinations. but before long, and certainly once you try to tackle some more-complicated features, you find yourself torn by an inherent conflict. starkly put, there is a

the trains are already leaving the station

i said: and get on board this new, better model, with a good algorithm. maybe the way you did it before was good enough for back then, but the future _will_ leave you behind if you do not get on board. _however_, you might want to wait, for maybe a month or two. because

on the curve

john macfarlane said: When you try to fit a curve to a bunch of data points (which is what writing more precise rules for Markdown involves), the best fitting curve will probably not pass through all of the points. you have shown a great ability to fit a curve to some disjointed points,

fast sailing on the way to a clearer model

john macfarlane said: CommonMark, which provides two implementations that use the same parsing algorithm, one in portable C and one in 1540 lines of javascript bingo. The javascript implementation doesn't use any unusual javascript features and should be straightforward to port

on syndromes and naming and promotion

michel said: I have some doubt it'll be fast enough in PHP. i don't enjoy telling you that you are wrong. certainly not when i know that it engenders your resistance. but i say it anyway, because you need to know when you are wrong. and i don't enjoy saying i told you so. certainly not

when rational discussion was still a possibility

michel said: If you want to start a discussion about that new Markdown-related thing making rounds on the internet i don't want to start such a discussion. but i find it very perplexing that so many of the people here -- who i assume are here because they _care_ about markdown -- would

that's pretty close to what i've done

# that's pretty close to what i've done gerald said: I'd say using a webcomponent (custom HTML element) with an HTML import should get you (almost) there. yes, that's pretty close to what i have done: http://zenmagiclove.com/misc/s/side-by-side-v4.html -bowerbird

what i meant by simple

# what i meant by simple ## table of contents what i meant by simple table of contents about the message i posted what gerald said what john said what i mean by simple my general responses my code was also less than perfect and now no framework required what this code facilitates on the matter