-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
breakage in toc; and doesn't report which file is bad #146
Comments
Looks like you ran into a bug. I had a quick look and the fix looked simple, so I think f2bee58 will fix it for you. Can you try again against git master? With regards to turning off link checking, there isn't currently a way to disable it.. However, I think that seems like a reasoble improvement to make if you are interested in giving it a go. |
I'm happy to try git master but not accustomed to Python and I don't see a BUILDING.md or similar file in the repo about how to work from the source tree. (I had done pip install.) Can you advise? I am in very early evaluation stage on the project, just trying to see if it will work for our needs, so I can't yet commit to patches, but if you can help me get going with the source, I might just start hacking. Update: I did |
Awesome, Thanks! For future reference, this is an easy way to do it too.
(of course, usual disclaimer about master not neccesarily being stable etc.) I've opened #150 to track the disabling of the link tracking. If you are happy with the other issue is fixed can you close this one? As a new user, any other feedback would be great in issues! Thanks :) |
I'd love to provide more detail than this spew, but:
I'm trying to convert an existing (doxygen) documentation set to mkdocs, incrementally, but I've found that mkdocs forces you to include in the document set every document which is linked to by any document -- if there is a single dead link, mkdocs won't build or serve. (Is there a command line flag to turn this strictness off?)
It worked for one file, and now I've added every file, and it's broken. Is there another way to debug? I can't take suspect file(s) out, because then whole docset won't build.
The text was updated successfully, but these errors were encountered: