diff options
| author | tim <tdixon51793@gmail.com> | 2011-12-20 03:50:19 -0600 |
|---|---|---|
| committer | tim <tdixon51793@gmail.com> | 2011-12-20 04:17:41 -0600 |
| commit | 7393f58c14d8dad6194c4845d545a3d7f7ccbf2e (patch) | |
| tree | 2a04a130837ee11f4f25a48878df54eb2b4cfba2 /tests/php/extra/Fenced Code Blocks.xhtml | |
| parent | 2e3830b9bf3a0829db7a5d04f731b5019d28cc65 (diff) | |
| download | markdown-7393f58c14d8dad6194c4845d545a3d7f7ccbf2e.tar.gz markdown-7393f58c14d8dad6194c4845d545a3d7f7ccbf2e.tar.bz2 markdown-7393f58c14d8dad6194c4845d545a3d7f7ccbf2e.zip | |
New footnotes configuration option: BACKLINK_TEXT (second try).
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.
Diffstat (limited to 'tests/php/extra/Fenced Code Blocks.xhtml')
0 files changed, 0 insertions, 0 deletions