similar to: A Single Test File?

I''m putting together a small web frontend for a client to upload files into an existing application. It''s trivial - there will never be more than a (small) handful of concurrent connections, but I need a streaming rack.input for upload progress on files up to 500MB or so. I was planning on using Rainbows! with ThreadSpawn and worker_connections=1, then noticed that unicorn is

Okay, it's pretty alpha, but it is a start. I have published "Markdown," which is a recipe that helps integrate Markdown syntax with PmWiki.[1] My goal is that, when finished, there will be something pretty close to a PHP-based wiki that relies on Markdown syntax. I have been involved with PmWiki for a couple years now. It has matured into a very potent, customizeable wiki engine.

I'm using the PHP port of Markdown, but I noticed the same effect on your dingus <http://daringfireball.net/projects/markdown/dingus> The problem I'm seeing is when I have an bulleted list and the last item of the list contains a block quote. The blockquote does not terminate correctly, and adding another blockquote after the list ends up extending the original blockquote.

So, this is my first post, greeting, yada, yada. By way of background, I'm a law student/former DC IT consultant and soon-to-return to the IT field. Don't ask me why I went to law school, I have forgotten--and I am not certain it was a good choice. I ran across Markdown only recently, although I have always favored ASCII as the impervious format. I'm also polishing my Python skills,

I just received a [bug report] for Python-Markdown complaining that colons are used in the ids of footnotes. For reference, we [output] the same format at PHP Markdown Extra. The general complaint is that the colon in the id attribute (`id="fnref:1"`) causes jquery to choke when referencing that id from javascript because jquery uses colons to indicate pseudo elements (as does CSS). As

Hi All, So I just joined the list - first off, Markdown is a great format and we're using it in our online community project disCourse: http://discourse.ics.hawaii.edu We're using markdown for our wiki pages, stories, message postings, pretty much everywhere. One markdown policy that doesn't seem to fit intuitively for our users is the fact that embedded underscores leads to

Hello List, Firstly, I was very impressed when I tried markdown 2.0 recently. Fantastic work all! I have a query about the treatment of emphasis. I realise that the horse has bolted, and changes to currently supported functionality are unlikely to attract support. However, there does seem (at least in my tiny mind) to be a mis-match between the following stated goal and the present

Does anyone have any toughts on how one should be using <video> & <audio> with Markdown? Using the link or the img syntax? Maybe: [a film](film.m4v) [an audio](audio.mp3) could create: <video src="film.m4v" controls><a href="film.m4v">a film</a></ video> <audio src="audio.mp4" controls><a

I am happy to announce the release of Python-Markdown 2.0 final. We have versions for Python 2.3-2.6 and Python 3.0! See the release notes here: https://sourceforge.net/project/shownotes.php?release_id=674043&group_id=153041 Download from PyPI here: http://pypi.python.org/pypi/Markdown/2.0 -- ---- \X/ /-\ `/ |_ /-\ |\| Waylan Limberg

We recently received the following bug report for the python-markdown implementation: > The "&" are escaped in URLs. > > An example: > [Link](http://www.site.com/?param1=value1&param2=value1) > > Should output: > <a href="http://www.site.com/?param1=value1&param2=value1">Link</a> > > Currently outputs: > <a

Hi I hope I haven't missed anything which answers this question on the syntax page, but what is the correct behaviour of the following markdown random text heading == random text # heading random text + list 1 (note there is not space before the '+') The following page treats the headings differently to the start of the list http://old-wp.slekx.com/the-markdown-tutorial/ That

Hi, I'm using the header id extension from markdown extra and in my perception it gets wrong when I use attributes on headers, for instance: >>> md = markdown.Markdown(['extra']) >>> md.convert('# My header {@class=red}') u'<h1 class="red" id="my_header_classred_1">My header </h1>' I would have expected:

Hello, I need to to slightly extend the markdown syntax. (place an image (img tag) in text which URL has not yet been determined). Therefore I want to define something like $[Alt text](img.jpg) which would be replaced by my pre-processor with  and then sent to markdown. Is there any special syntax that should be used for such 3rd party extensions? How would you do

I just received a report [1] that the footnote output we use in Python-Markdown (an exact copy of PHP Markdown Extra [3]) is not valid HTML [3]. If you notice he's using HTML5. At least the footnote syntax does valid on XHTML1 or HTML4. Anyway, any suggestions on how the various footnote implementations want to move forward with this? [1]: https://github.com/waylan/Python-Markdown/issues/129

Howdy, Quick question: Since list items with multiple paragraphs need to be indented four spaces, and code blocks are also indented four spaces, is there any way to disambiguate a list followed by a code block? Example: * This is a list item. * And so is this. Is this a second paragraph in the second list item, or a code block? It looks like Markdown.pl and discount

// hoping this is sufficiently on-topic // php-driven, markdown-aware, open source wiki/cms that has some degree of version control, a flexible system for privs/access control, is installable (or buildable) on OS X and has an easy installer for windows ?

Hi, first of all thanks for such a great syntax, so far it's the best I know! I have a document with quite long titles and I was wondering if it was possible to hard-break them: e.g.: This is a veeeeeeeeeeeeeeeeeeerrrrrrrrrrrrry long title ======================================================= would be This is a veeeeeeeeeeeeeeeeeeerrrrrrrrrrrrry

> Anyway, a spec for Markdown Extra would contain a spec for Markdown as > well, wouldn't it? I think the whole enterprise would be a lot more valuable, if we produce a combined spec, which would be self-contained, and call it Markdown 2.0. I don't think we necessarily need a formal grammar. What we need is to create a document, starting with "Markdown Syntax" perhaps,

Hi folks, Yesterday I raised an issue about inconsistent preservation of whitespace<http://www.freewisdom.org/projects/python-markdown/Tickets/000087>in Python-Markdown. >>> import markdown >>> md = markdown.Markdown() >>> md.convert('Added `>>> ` to signify user input.') u'<p>Added

We recently received a request and working patch for Python-Markdown which adds support for starting an ordered list with the number given on the first line. For example: 3. Foo 4. Bar would result in <ol> <li start="3">Foo</li> <li>Bar</li> </ol> I'm not opposed to adding this, but I noticed that no other implementation