| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\
| |
| | |
edited setup docs for CodeHilite with Pygments
|
|/
|
| |
Improved the setup documentation when rendering Python code with Pygments and CodeHilite. Added a link to the Pygments CSS files and emphasized that not installing pygments does not cause an error message.
|
|\
| |
| | |
Convert readthedocs link for their .org -> .io migration for hosted projects
|
|/
|
|
|
|
|
|
| |
As per [their blog post of the 27th April](https://blog.readthedocs.com/securing-subdomains/) ‘Securing subdomains’:
> Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard.
Test Plan: Manually visited all the links I’ve modified.
|
|
|
| |
Fixes #475.
|
|\
| |
| | |
README - add link to changelog
|
|/
|
|
| |
Fixes #474. Makes it a bit easier to find the changelog.
|
|\ |
|
| |\
| | |
| | | |
Support CodeHilite option use_pygments in fenced_code
|
| | | |
|
| |/ |
|
| |\
| | |
| | | |
Fix lazy ordered list example in documentation
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The documentation is not accurate when lazy_ol=False parameter is called.
The example shows the 'start' attribute to the first <li> tag. However, the attribute is in the <ol> tag:
>>> import markdown
>>> s = """
... 4. Apples
... 5. Oranges
... 6. Pears"""
>>> markdown.markdown(s, lazy_ol=False)
u'<ol start="4">\n<li>Apples</li>\n<li>Oranges</li>\n<li>Pears</li>\n</ol>'
The behaviour of the library is the correct one (https://developer.mozilla.org/fr/docs/Web/HTML/Element/ol), so the documentation need to be fixed, not the library.
|
|/
|
|
|
|
| |
The statement will never evaluate False, so its not needed.
Also, Unicode is not valid for PY3, so its better to not include it.
Fixes #470.
|
| |
|
|\
| |
| | |
Toc bug
|
| |
| |
| |
| | |
Removing items while iterating can result in wrong behavior. Refs #461.
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
| |
New versions of Pygments insert <span></span> blocks in the beginning
of the generated output sometimes [1], so we need to remove those blocks
before doing the actual checking.
[1]: https://bitbucket.org/birkenfeld/pygments-main/commits/164574c13533
|
|
|
|
|
|
|
| |
Now it should no longer print internal errors instead of intended ones
on Python 3.
Thanks to Maurice van der Pot for finding this fix.
|
| |
|
|
|
|
|
| |
The failure printed when self.assertTrue was used with str.startswith
did not show the string that was being searched.
|
| |
|
|
|
|
|
|
| |
Added pygments to test-requirements and updated codehiliting tests to
only test partial output as output differs depending on Pygments version.
Fixes #453
|
|
|
|
| |
That way py32 tests can still be run locally. Just not on the CI server.
|
|
|
| |
Pip version 8 dropped support for Python 3.2 and by testing it we are getting errors (related to pip, not Markdown) on that version only. Removing the Py32 tests for now so our automated tools continue to work.
|
|
|
| |
The `downloadcache` config value is deprecated by tox and the related `--download-cache` flag is removed on pip version 8.0 (deprecated in 6.0). With this change tests should run with the lasted versions of all tools (they do not without it).
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix #440 (Tables extension drops characters after code spans)
|
| |
| |
| |
| | |
Fixes #440. Thanks @jandecaluwe for the bug report.
|
|/ |
|
| |
|
|
|
|
|
|
| |
Drppoed the non-greedy quantifier from the end of the inlinePatterns as it
served no useful purpose and was actually (in very rare edge cases) causing
newlines to be dropped. FIxes #439. Thanks to @munificent for the report.
|
| |
|
|\
| |
| | |
Table inline code
|
| | |
|
|/
|
|
| |
must stick with coverage<4.0.
|
|\
| |
| | |
Fix infinite loop #430
|
|/
|
|
|
|
|
|
|
| |
This should fix the remaining corner cases that can cause infinite
loops. Previous iterations did not account for scenarios where the
“end” index was less than the “start” index. If the “end” index is
ever less than or equal to the “start” index, the “end” will be
adjusted to to be “start” + 1 allow the full range to be extracted and
replaced.
|
|\
| |
| | |
Fix find footnote placeholder to recurse
|
|/ |
|
|\
| |
| | |
Use a different approach to fix the smarty bug
|