diff options
| author | tim <tdixon51793@gmail.com> | 2011-12-20 17:50:19 +0800 |
|---|---|---|
| committer | Mike Dirolf <mike@dirolf.com> | 2012-01-15 00:45:35 +0800 |
| commit | 1a291cf491a8e6aa4a2e602f5f732d1092fba2a6 (patch) | |
| tree | 5dfd061dd43b6b8b4109c225a71aa51c50fa6fa3 /tests/basic/links-inline.txt | |
| parent | 425fde141f17973aea0a3a85e44632fe18737996 (diff) | |
| download | markdown-1a291cf491a8e6aa4a2e602f5f732d1092fba2a6.tar.gz markdown-1a291cf491a8e6aa4a2e602f5f732d1092fba2a6.tar.bz2 markdown-1a291cf491a8e6aa4a2e602f5f732d1092fba2a6.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/basic/links-inline.txt')
0 files changed, 0 insertions, 0 deletions