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

Add links behind nav entries "Namespaces" and "Files" (matching "Classes") #568

Merged

Conversation

kossebau
Copy link
Contributor

When layout file has "namespacelist" and/or "filelist" set to visible=no,
the files "namespaces.html" resp. "files.html" are still generated,
but not reachable.

So same fix as done for "classlist" should be used,
cmp. 700a9ac

Also gives a consistent result & at least in generated QCH files fixes the error
message currently shown when clicking on "Namespaces" or "Files" section titles in the navigation tree.

Using lne->baseFile() and thus the string from the central db instead of using a hardcoded duplicated filename feels better, and thus first patch also adapts the code for "LayoutNavEntry::Classes".

…ses")

When layout file has "namespacelist" resp. "filelist" set to visible=no,
the files "namespaces.html" resp. "files.html" are still generated,
but not reachable. So same fix as done for "classlist" should be used,
cmp. 700a9ac

Also gives consistent result & at least in QCH files fix the error
message shown when clicking on "Namespaces" or "Files" section titles.
@kossebau kossebau force-pushed the makeNavEntriesNamespacesAndFilesLinked branch from 135280e to 464919a Compare June 13, 2017 16:42
@kossebau
Copy link
Contributor Author

Rebased the commits to latest master, but again Travis dies during

Get:7 http://ppa.launchpad.net/texlive-backports/ppa/ubuntu precise/main amd64 texlive-latex-extra-doc all 2012.20120611-1~ubuntu12.04.1 [293 MB]

with

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

Meh. This spoils the otherwise nice idea of CI, if one gets flagged Red only because CI is failing elsewhere :/

All I can say is that locally the patch builds fine and also works as expected for mw :)

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

Successfully merging this pull request may close these issues.

None yet

4 participants