Skip to content

.rst table of contents link do not work #71

Closed

Description

@miohtama

E.g. on page

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

TOC hash links do not work.

Activity

  1. shino commented on Aug 29, 2011

    @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.

  2. vitorbrandao commented on Dec 3, 2011

    @vitorbrandao

    I have the same problem. Any workaround?

  3. pdurbin commented on Apr 14, 2012

    @pdurbin
  4. wyuenho commented on Dec 16, 2012

    @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.

  5. wyuenho commented on Nov 5, 2013

    @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

  6. eliben commented on Jun 7, 2014

    @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.

  7. laymonage commented on Apr 8, 2019

    @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.

  8. kivikakk commented on Apr 9, 2019

    @kivikakk
    Contributor

    👋 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.

  9. locked as off topic and limited conversation to collaborators on Apr 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions