make links to duplicate index entries predicatable

Anonymous avatarAnonymous created an issue

tldr: sort indexentries.iteritems to get predictable link order in document index

I've constructed a set of documents where I have individual documents and an all-in-one document that includes each individual document. For example:

a.rst b.rst c.rst all.rst include a, b, c index.rst toctree: a, b, c, all

When creating a master index (genindex) I get 2 links for each index entry as expected - one that points to the individual document (a.rst or b.rst, for example) and one that points to the all-in-one document (all.rst).

However, I find that sometimes the first link points to the individual document and other times the first link points to the all-in-one document.

My choice would be to have the index generation be more stable and predictable.

I've found that if I place all my individual documents in a sub-directory and then sort the indexentries in sphinx.environment.create_index I get a stable and predictable index ordering.

< for fn, entries in self.indexentries.iteritems():

for fn, entries in sorted(self.indexentries.iteritems()):

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.