The python markdown project had been stagnating until recently due to
the lack of time on my part. Waylan now agreed to start helping out
with the project, so we'll hopefully be making some progress in terms
of triaging old tickets, setting up and updating a new wiki, etc.
In terms of Extra, the
I'm not sure the indentation feature is so useful. After all, you can use
the old syntax if you want indentation. What do you think?
I'd prefer to keep it simple and leave out the indentation feature.
I'm not against option 2, but I don't see it as a replacement to option 1
(for the
On 10/6/07, Lou Quillio [EMAIL PROTECTED] wrote:
[snip]
Wish there were an 'Extra' for Python.
There is. Sort of. Python-Markdown has an extension interface [1].
There's a number already available and its fairly easy to write your
own. I've slowly been adding many of php extra's features [2].
Figures, I respond to the old discussion, then see the new one. Oh
well, Micheal covered my points in more detail here.
On 10/7/07, John MacFarlane [EMAIL PROTECTED] wrote:
[snip]
On (b): Non-extended markdown parsers will make a mess of the
new code blocks with either syntax, since they won't
Howdy,
The following bug report was sent to the Debian BTS. Is there a way
to have a code block immediately follow an unordered list?
- Forwarded message from Joey Hess [EMAIL PROTECTED] -
Consider this markdown:
* bla
* bla2
this should be treated as code block
and it is not
Matt Kraai wrote:
If the first code block is indented with 8 spaces, or 2 tabs, it will be
treated as a nested code block inside the second list item, but there seems
to be no way to make it be seen as a code block that immediately follows
the list.
A known shortcoming.
* Matt Kraai [EMAIL PROTECTED] [2007-10-07 02:55]:
there seems to be no way to make it be seen as a code block
that immediately follows the list.
Clumsy, but there is:
* bla
* bla2
!-- --
this should be treated as code block
Regards,
--
Aristotle Pagaltzis //
Michel Fortin wrote:
Note that creating a second paragraph in the list item is correct
behaviour, not a bug.
And I should've been clearer that it's not a bug, and should've
linked directly to the workaround. Apologies.
So I'm seriously thinking about adding a second (unindented) code block
So I'm seriously thinking about adding a second (unindented) code block
syntax to PHP Markdown Extra that would avoid this issue entirely.
Something like this:
Regular paragraph
~~~
Code block
~~~
I like the idea of doing something about this problem. I've been
