Inserting links after <hr> fails?
-
Case A
Text
Not turning into a link: [Foo](#foo)Code:
Text <hr> Not turning into a link: [Foo](#foo)
Case B
Text
Turns into a link: [Foo](#foo)Code:
Text <hr> Turns into a link: [Foo](#foo)
I would expect the
[Foo](#foo)
to turn into a link in both cases.
-
Confirmed.
Alternatively:
Text --- [Foo](#bar)
produces:
Text
Text --- [Foo](#bar)
produces:
Text
Not sure if that would be considered a bug, and it's pretty much well known, but adding it here for completeness sake.
-
I believe this one is worth a look @eviltrout.
-
Interesting edge case.
In this case the workaround is to use Markdown instead of HTML for your horizontal rule:
<hr>
---
-
According to the tutorial, we can use footnotes using the following syntax:
[text][ref#] … [ref#]: Text
This works if we have one footnote, but not more than one. So whilst
this text is footnoted[1][1] [1]: Footnote
(no idea what's going on with that code box)
produces the expected result with a link to the footnote, the following produces something else entirely.
this text is footnoted[1][1] twice[2][2] [1]: Footnote [2]: Another Footnote
As an aside, the footnote link text should be subscripted.
-
-
Nice example. Thanks!
-
Per http://superuser.com/editing-help#basic-links
What might be tripping you up there is that it's odd to duplicate the text exactly, e.g.
Here is a link to [Google][g]. [g]: http://google.com
versus
Here is a link to [g][g]. [g]: http://google.com
Also, by "footnote", we mean "hyperlink". So this is also weird:
Here is a link to [Google][g]. [g]: Footnote
-
Also, by "footnote", we mean "hyperlink".
Say what you mean! Especially in user documentation; users won't read it much, but when they do, they're looking for help and are already muddled so it doesn't do to add to their confusion.
-
I are confused by all this newfangled footnote business.
-
[Nevermind; repro confirmed]
-
So say what you mean. "Footnote" is a well defined concept1 - it's a reference to an "out of flow" explanation or expansion which would be too large to (for example) put in parentheses and allow the reader to keep the flow of where they are.
Obviously, this post is a pretty good example of what I was expecting from "footnotes".
1 It might contain a link (or maybe even more2) but generally it's gonna be a bunch of word salad. As a rule, if your interjection / explanation / expansion spreads to more than one sentence, it's best expressed as a footnote.
2 Maybe even to other footnotes.
-
So say what you mean
I never said "footnote". The documentation I wrote is at http://superuser.com/editing-help
-
Still a repro
Text <hr> Not turning into a link: [Foo](#foo)
Text
Not turning into a link: [Foo](#foo)That linebreak above the
<hr>
is significant for some reason. One workaround is to simply put a space in front, like so:Text <hr> Not turning into a link: [Foo](#foo)
which produces
Text
Not turning into a link: [Foo](#foo)
-
FWIW, both appear to be links in the post above:
But I can still repro the bug in the preview editor (and in the actual post as it turns out):
Text
Not a link: [Foo](#foo)Text
Link: [Foo](#foo)Workaround
Link: [Foo](#foo)Unrelated, but IMO the placement of the <hr> is a bit weird. It's always attached to the text above, where I would expect
Text <hr> Foo ``` to result in something more like Text <hr>Foo. rather than Text <hr> Foo.
-
Sorry I accidentally had the workaround in my post -- the space before the
<hr>
-
This post is deleted!