Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use unique anchor tags for each item in the table of contents #12

Closed
hi5 opened this issue Aug 15, 2014 · 7 comments
Closed

Use unique anchor tags for each item in the table of contents #12

hi5 opened this issue Aug 15, 2014 · 7 comments

Comments

@hi5
Copy link
Contributor

hi5 commented Aug 15, 2014

Be sure to use unique anchor tags for each item in the table of contents, I've fixed it by adding the category prefix e.g. scripts-clipboard, scripts-gui etc. Simply create a named anchor like so:

<a name="scripts-gui"></a>
@vasili111
Copy link
Member

@hi5
👍
I just found that bug and posted question at Github asking how to fix it http://stackoverflow.com/questions/25330368/two-group-links-with-the-same-name-should-link-to-different-places
Only after posting question I found your fix.

@hi5
Copy link
Contributor Author

hi5 commented Aug 16, 2014

I just noticed that GH already seems to fix this issue, if you hover over the permalink icon of a heading (the shackle on the left of the heading) you'll see that for the second Gui anchor it has added a -

First gui https://github.com/ahkscript/awesome-AutoHotkey#gui
Second gui https://github.com/ahkscript/awesome-AutoHotkey#gui-

@vasili111
Copy link
Member

@hi5
Just tested it here: https://github.com/vasili111/awesome-AutoHotkey
You are right, it works. I think it is better way then using html tags.

@rshipp
Copy link
Member

rshipp commented Aug 17, 2014

This will break links in the TOC if you add a heading with the same name in a previous section, so we'd have to be careful to keep them updated.

@vasili111
Copy link
Member

@rshipp Yes you are right. In that case using html tags looks better

@rshipp
Copy link
Member

rshipp commented May 5, 2015

This issue is linked in contributing.md, can it be closed now?

@vasili111
Copy link
Member

I think yes. If someone will need it we can reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants