aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
| * Add new utility function parseBoolValue()Dmitry Shachnev2013-09-254-23/+20
| | | | | | | | and use it in all extension that need parsing bool config values.
* | Merge pull request #256 from eichin/patch-1Waylan Limberg2013-09-261-1/+1
|\ \ | |/ |/| Update __init__.py
| * Update __init__.pyMark Eichin2013-09-261-1/+1
|/ | | spelling.
* Merge pull request #247 from vhf/patch-1Waylan Limberg2013-09-181-1/+1
|\ | | | | Typo fix
| * Typo fixvhf / victor felder2013-09-091-1/+1
| |
* | Merge pull request #251 from me-and/wikilinks-sWaylan Limberg2013-09-181-26/+26
|\ \ | | | | | | Add missing "s" to wikilinks documentation. Fixes #250.
| * | Clean trailing whitespaceAdam Dinwoodie2013-09-191-21/+21
| | |
| * | Correct documentation: `wikilink` -> `wikilinks`Adam Dinwoodie2013-09-191-6/+6
|/ / | | | | | | This fixes #250.
* | Merge pull request #249 from lvella/masterWaylan Limberg2013-09-111-1/+1
|\ \ | |/ |/| Fix: "AttributeError: 'dict_items' object has no attribute 'sort'"
| * Fix: "AttributeError: 'dict_items' object has no attribute 'sort'"Lucas Clemente Vella2013-09-111-1/+1
|/ | | | Happens on pip install with Python 3.
* Merge pull request #246 from FND/patch-1Waylan Limberg2013-09-041-1/+1
|\ | | | | fix typo
| * fix typoFND2013-09-041-1/+1
|/
* Ensure each term on def list maintains its own loose status.Waylan Limberg2013-09-023-2/+23
| | | | | | Previously, the code was ignoring whether this was a new term when determining whether the currect item should be loose or not. Fixes #243. Thanks for the report @Anomareh.
* Merge pull request #244 from Grahack/patch-3Waylan Limberg2013-08-241-1/+1
|\ | | | | Typo in util.py
| * Typo in util.pyGrahack2013-08-241-1/+1
|/ | | implemenation -> implementation
* Allow fenced_code to be configurable in subclasses.Waylan Limberg2013-08-191-10/+9
| | | | | Not sure why I was using global variables here. Anyway. Fixed now. Thanks to Andrew for pointing it out.
* Added release notes for pending release of v2.4.Waylan Limberg2013-08-134-5/+53
| | | | | Since adding the new smarty extension, the nex release it more than just a bugfix release.
* Deprecated CodeHilite's force_linenos config setting.Waylan Limberg2013-08-131-1/+1
| | | | It was previously marked pendingdeprecation in v2.3. Now deprecated.
* Extended headerid's rawHTML in id handling to toc ext.Waylan Limberg2013-08-112-16/+20
|
* Allow extensions to register serializersWaylan Limberg2013-08-073-8/+28
| | | | | | | | | Setting output_format must happen after extensions are loaded. Only in that way can an extension register a serializer so that it will then be available to be used with the output_format keyword. A test has been added to avoid this regression from happening again in the future. Fixes #238, partially reverses commit 41cc055 and provides a better fix for
* Serializers now preserve case of tags.Waylan Limberg2013-08-072-4/+35
| | | | | | | It is up to the markdown code (and extension authors to make sure tags are of the correct case (there may be cases were an extension might need to mix cases - which should be preserved). Fixes #237. Thanks for the report @eichin.
* HeaderID Ext now handles raw html in ids. Fixes #232Waylan Limberg2013-07-283-2/+32
|
* Fix Python 3 compat in Attr_list. Fixes #218.Waylan Limberg2013-07-281-1/+1
|
* Merge pull request #233 from mitya57/run-test-fixWaylan Limberg2013-07-281-1/+1
|\ | | | | Fix NameError in run-tests.py
| * Fix NameError in run-tests.pyDmitry Shachnev2013-07-281-1/+1
|/
* Merge pull request #231 from mitya57/masterWaylan Limberg2013-07-2810-5/+344
|\ | | | | Add Smarty extension and use it for building docs.
| * Some fixes requested by @waylan, cleanup and tests improvementsDmitry Shachnev2013-07-273-13/+20
| |
| * Use smarty extension when building docsDmitry Shachnev2013-07-261-1/+1
| |
| * Add documentation for smarty extensionDmitry Shachnev2013-07-265-4/+63
| |
| * Add smarty extension, based on SmartyPants libraryDmitry Shachnev2013-07-264-0/+273
|/
* Added support for attr_lists on definition list terms.Waylan Limberg2013-07-194-4/+24
| | | | | | | | Like headers (h1-6) dt's can only be on one line, so we need to use the header regex on dt's. This was implemented after considering a recent [discussion](http://six.pairlist.net/pipermail/markdown-discuss/2013-July/002859.html) on the markdown mailing list. Prior to that discussion, I never considered that it was impossable to set block level attrs on dt's. Now it is.
* Allow inline attr_lists at end of header.Waylan Limberg2013-07-193-3/+3
| | | | | | | | | | A header can be only one line - so unlike other block level elements, a attr_list must be at th eend of the line. To disingush it from an inline attr_list on the last child in a header, we must require at least one space before th eblock-level attrt_list. Always intended it to work that way. Not sure how I missed that before. At least we're testing for it now.
* Attr_List Extension now also supports nested ol's.Waylan Limberg2013-07-193-12/+54
| | | | | | | | | | Not sure how I missed that when committing ea4af0d. Also as a side-effect, this fixes #230 - which brought my previous oversight to my attention. Thanks for the report @divisoryang. Also added some tests - including tests of list items without attr_lists. Sometimes I forget to test markup that does not use an extension when an extension is enabled. That's what resulted in #230 being reported.
* MetaData no longer fails with no newline. Fixes #228.Waylan Limberg2013-07-032-1/+8
|
* Minor cleanup.Waylan Limberg2013-06-161-1/+0
|
* Attr_List Extension now support attr_lists on nested lists.Waylan Limberg2013-06-163-2/+51
| | | | | | A list item with a nested list complicates were the attr_list can be. Fixes #218. Thanks for the report @jpzimmer.
* Fixed wikilinks extension's handling of config setting. Not sure how I ↵Waylan Limberg2013-06-161-2/+2
| | | | didn't notice the tests were failing for this before.
* Improved codehilite docs. Document `css_class` setting.Waylan Limberg2013-06-161-5/+13
| | | | | | Also cleaned up poor wording on other setting for codehilite. Thanks for the inital suggestion @davidcorne. Fixes #223.
* AbbrExtension now handles abbreviations nested in other markup.Waylan Limberg2013-06-162-2/+11
| | | | | | | | Just set each abreviation as an AtomicString. Given the nature of abbreviations, they are not likely to ever contain any other markup anyway. Also added a test. Fixes #224. Thanks for the report @JakeChampion.
* Fixed #216. WikiLink Extension actually accepts configs.Waylan Limberg2013-05-191-2/+2
|
* Updated extension API docs to list output_format and serializer on the md ↵Waylan Limberg2013-05-091-6/+9
| | | | | | | | | instance. I still need to document everything on that list and probably a few things missing from the list. I also updated the warning about monkey patching to be a "Warning" admonition - now that we have that extension. Probably should depreciate access to md_globals in the extension API -- as we don't actually use any anymore. That dates back to pre-OO code.
* Merge pull request #212 from shvechikov/patch-1Waylan Limberg2013-04-151-1/+1
|\ | | | | Fixed a typo in the docs
| * Fixed a typo in the docsLeonid Shvechikov2013-04-151-1/+1
|/
* Merge pull request #207 from mitya57/cleanupWaylan Limberg2013-03-234-11/+4
|\ | | | | Some minor code cleanups
| * odict.py: remove usage of iteritems_compat which was not workingDmitry Shachnev2013-03-231-8/+3
| | | | | | | | | | | | | | | | | | I've added iteritems_compat function in one of my previous pull requests, which was failing with: ./markdown/odict.py:106: undefined name 'iteritems_compat' This commit drops usage of that function.
| * Remove some unused importsDmitry Shachnev2013-03-233-3/+1
|/
* Version 2.3.12.3.1.finalWaylan Limberg2013-03-221-1/+1
|
* Added a note about tox in test suite docs.Waylan Limberg2013-03-191-1/+7
|
* Ensure handleAttributes doesn't lose AtomicStrings.Waylan Limberg2013-03-181-3/+3
| | | | | | | | | | | | | | | Fixes #204. This was a real pain to debug. But I think the problem stemmed from the fact that the footnote extension inserted a etree link into the footnotes last p element. Then when inline patterns are run, the inline code in that p element is processed. Normally, code would be the first child found, but with the pre-existing link, that wasn't the case and the parser took a slightly differant path which would never be encountered in any other situation. It was this slightly differant path that made the lose of the AtomicString status of the inline code matter. Since any AtomicString (including inline code) doesn't need to be run though hanldeAttributes anyway, we can just skip over it and preserve the AtomicString. Whew!
* Merge pull request #205 from Gamma3000/future-orderWaylan Limberg2013-03-1823-33/+36
|\ | | | | Future statement ordering
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 21:53:53 +0000