.rst table of contents link do not work

[miohtama]

E.g. on page

https://github.com/epeli/sauna.reload

TOC hash links do not work.

[shino]

I am in trouble with the lost hyper links in rst content directive.

When I write a rst document of a few hundreds lines, I can't make links to sections.
And I can't use urls those specify lines like https://github.com/epeli/sauna.reload/blob/master/LICENSE.txt#L9 .

If content directives of reStructuredText are not supported, it is much useful to render rst files as plain text, so that we can use links specifing any lines.

[vitorbrandao]

I have the same problem. Any workaround?

[pdurbin]

I can't seem to link to a specific line in a reStructuredText document either (i.e. https://github.com/saltstack/salt/blob/d518dcb9462bae247cb7c5db985903c90396f0b7/doc/topics/tutorials/states_pt2.rst#L77 doesn't work), as I mentioned at https://plus.google.com/107770072576338242009/posts/DBWrTmdr3ES

[wyuenho]

I see the same problem too. The problems seems to only happen for TOC links that has a . in the header. Removing it should make the anchors works.

[wyuenho]

Automatic section numbering probably should be turned off for ReST docs that has a TOC.

http://docutils.sourceforge.net/docs/user/config.html#sectnum-xform

[eliben]

I'm experienced the same problem in https://github.com/eliben/pycparser

The README file uses sectnum for section numbers, and this prevents TOC links from working. Looking at the links, I see that while the TOC points at something like https://github.com/eliben/pycparser#introduction, in reality the anchor is https://github.com/eliben/pycparser#1introduction -- the prepended section number is missing.

[laymonage]

This seems to be broken in gists, regardless of section-numbering. It worked fine a few days ago, and it still does on repos. Here is an example, taken from the link in the OP. It still works fine in the original repo.

[kivikakk]

👋 Please reach out to our support team with your bug report — this repository is no longer the correct place for bugs relating to the website, only for issues within the github-markup gem itself.