| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this patch, it was possible to pass a list of extensions and
parameters to use when instantiating a new Markdown instance, but it was
not possible to give a full module name; the extension had to be a
submodule in markdown.extensions.
Now we allow giving a full module path, to make it easy to use custom
extensions which are not bundled within the markdown package. The
previous behaviour has been retained when there is no '.' in the
extension name.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is an extension which alters the behavior of lists to be less surprising.
If turned out to be rather simple to code. I'm surprised no one had written it
yet.
I should note that this extension does not generate separate lists if different
unordered list markers are used (`*` verses `-` verses `+`) The way the parser
works that would be a little more tricky.
|
| |
| |
| |
| |
| | |
This will make it easier for extensions to subclass the list block processors
and alter their behavior. Such as the request in issue #64.
|
| | |
|
| |
| |
| | |
I forget about this now that we have a git log and release notes.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The footnotes treeprocessor must be the first one run so that all others,
including codehilite's, can run on the contents of the footnote div which is
created and inserted by the footnotes treeprocessor.
Thanks to startling for the report.
|
| |
| |
| |
| |
| |
| | |
Codehilite generates differant output with differant versiosn of pygments.
We support those various versions of pygments but can't unsure that the
same version is always available on every platform tests are run on.
|
| | |
|
| |
| |
| |
| |
| | |
Not only does this ensure that all output matches the output_format,
but it is nessecary to run in Python 3.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Final fix to issue introduced in fix for #59. Weird stuff inside
angle brackets now also work in safe_mode='escape'. We just did the
same thing as with block html, let the (x)html searializer do the
escaping. Tests updated including the standalone test moved to match
the non-escape cases.
|
| |
| |
| |
| |
| | |
Markdown markup inside angle bracktes now gets rendered properly
in all cases except when safe_mode='escape'. Also added tests.
|
| |
| |
| |
| |
| |
| | |
Replaced the unescape method I carlessly threw in the RawHtmlProcessor.
Unfortunetly, this reintroduces the bug just fixed in commit
425fde141f17973aea0a3a85e44632fe18737996 Sigh!
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
markdown/inlinepatterns.py
|
| | |
| | |
| | |
| | | |
type.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
See tests/html4_safe/html_then_blockquote.(txt|html).
It looks like having unclosed block-level html elements was causing
further processing not to happen, even in the case where we're
escaping HTML. Since we're escaping HTML, it seems like it shouldn't
affect processing at all. This changes output results in a couple
of other tests, but the new output seems reasonable to me.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Interestingly, the change to the misc/mismatched-tags test is inline with
PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Apparently, in Python3 stdin and stdout take str (unicode) not bytes.
This provides a solution that will work in both python 2 & 3.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also optimized the code to bypass parsing when not in safe_mode and return
immediately upon failure rather than continue parsing when in safe_mode.
Note that in Python2.7+ more urls may fail than in older versions because
IPv6 support was added to urlparse and it apparently mistakenly identifies some
urls as IPv6 when they are not. Seeing this only applies to safe_mode now,
I don't really care.
|
| | |
| | |
| | |
| | | |
work with it.
|
| | |
| | |
| | |
| | | |
capitalized. Thanks for the report.
|
| | |
| | |
| | |
| | |
| | | |
I accidentally changed the wrong line (L294 instead of L293) to
"self.footnotes.getConfig("BACKLINK_TEXT")" before. This fixes that.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
BACKLINK_TEXT specifies the text that's used in the link at the end of
the footnote to link back up to the reader's place. It still defaults to
"↩".
Okay, so at first I had an uncessarily complicated commit for this and
submitted a pull request. Waylan showed me a better way to do it, here:
https://github.com/startling/Python-Markdown/commit/ee7d1a26c76f970c12226ca48ba52dc1d32f2488#markdown/extensions/footnotes.py-P19
So I made another commit and added it to the pull request. But then I
accidentally added yet another commit to the pull request, accidentally.
Since then, I've realized it would be best to start with a new branch
and closed that first pull request.
Hopefully this will be the last try.
|
| | |
| | |
| | |
| | | |
mode on.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Interestingly, the change to the misc/mismatched-tags test is inline with
PHP Markdown Extra's behavior but not markdown.pl, which produces invalid html.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Apparently, in Python3 stdin and stdout take str (unicode) not bytes.
This provides a solution that will work in both python 2 & 3.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Also optimized the code to bypass parsing when not in safe_mode and return
immediately upon failure rather than continue parsing when in safe_mode.
Note that in Python2.7+ more urls may fail than in older versions because
IPv6 support was added to urlparse and it apparently mistakenly identifies some
urls as IPv6 when they are not. Seeing this only applies to safe_mode now,
I don't really care.
|
| | |
| | |
| | |
| | | |
work with it.
|
| | |
| | |
| | |
| | | |
capitalized. Thanks for the report.
|
|\| |
| | |
| | | |
Allow backticks in addition to tildes for code blocks in the fenced_code extension
|
| | | |
|
| | |
| | |
| | |
| | | |
extension source
|
| | | |
|
| | |
| | |
| | |
| | | |
used by github
|
|\ \ \
| |/ /
|/| | |
New footnotes configuration option: BACKLINK_TEXT
|
| | |
| | |
| | |
| | |
| | | |
I accidentally changed the wrong line (L294 instead of L293) to
"self.footnotes.getConfig("BACKLINK_TEXT")" before. This fixes that.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BACKLINK_TEXT specifies the text that's used in the link at the end of
the footnote to link back up to the reader's place. It still defaults to
"↩".
Okay, so at first I had an uncessarily complicated commit for this and
submitted a pull request. Waylan showed me a better way to do it, here:
https://github.com/startling/Python-Markdown/commit/ee7d1a26c76f970c12226ca48ba52dc1d32f2488#markdown/extensions/footnotes.py-P19
So I made another commit and added it to the pull request. But then I
accidentally added yet another commit to the pull request, accidentally.
Since then, I've realized it would be best to start with a new branch
and closed that first pull request.
Hopefully this will be the last try.
|
| | |
|
| |
| |
| |
| | |
previously merged). Thanks Marcin. Also added a test for not-indented secondary lines of a first paragraph in a footnote definition.
|
|\ \ |
|
| |/ |
|
| |
| |
| |
| | |
code to provide a few other minor improvements s that output more closely matches php's output. Thus the changes in the tests.
|