Regarding the URL handling, I also used to hate it, but wrote a tool to make it easier to deal with; details are here if you're interested (despite the title, the relevant tool is not Vim-only): <http://tadhg.com/wp/2012/10/07/tools-for-writing-restructure...;
Re:The Future of Markdown
by rogerbinns on Friday October 26, 2012 @01:34AM
(#4700984)
The bit I hate is that I have no desire to have a global list of URLs and manage them. So instead I have to put a double underscore suffix after every url otherwise you get bizarre error messages. eg `foo <foo.com>`__
Re:The Future of Markdown
by bookweevil on Friday October 26, 2012 @12:15AM
(#4700853)
Have you tried using the list-table directive? I find it's a much easier way to create tables - it's based on writing indented lists which mirror the logical structure of the table (i.e., table / row / cell), rather than trying to produce ASCII art.
Re:The Future of Markdown
by rogerbinns on Friday October 26, 2012 @01:39AM
(#4700999)
It isn't listed in the Sphinx doc http://sphinx.pocoo.org/rest.html#tables - and it points to rst doc only showing those two as well http://docutils.sourceforge.net/docs/ref/rst/restructuredtex...
All my doc is in Sphinx so I play it safe, and all directives need to be supported in whatever version of docutils and rst2pdf are installed across the various developer machines. So for the moment I am stuck with ascii art.
Re:The Future of Markdown
by gordonguthrie on Friday October 26, 2012 @12:21PM
(#4702902)
But sphinx produces tables with an inline border="1" in them.
Plowing through the sources to figure out where that happens... (docutils?).
Any thoughs/pointers would be welcome from a passing reader of this comment...
I hate its URL handling.
And of course it needed Sphinx to make it work across more than one source file which means we now have two dialects.
I do wish everyone would just agree on one syntax and be done with it.