fix xonsh links

[scopatz]

Should fix #13 CC @gonuke @FlanFlanagan

[gonuke]

Still looks like there is one lingering reference to xonsh

[gonuke]

Should the 2nd entry still be xonsh.tex?

[scopatz]

Whoops! fixed!

[gonuke]

LGTM - thanks @scopatz

[gonuke]

Does this automatically get deployed? Or do I need to (figure out how to) do that?

[scopatz]

It seems that doctr is set up on this repo, so it should have already been deployed.

[gonuke]

cool - this is my first look at doctr... I can't help but feel like new docs will be pushed by doctr for every PR... it that correct? intended?

[scopatz]

Yes, I think that is what is happening. I think the idea is that the docs are built for every PR (as a test) and then when the PR is merged, the docs are built again and actually deployed (pushed to the github pages repo).

[gonuke]

But it appears that the docs are deployed each time a PR is tested... or is doctr wise enough to avoid that?

[scopatz]

I think it depends on how it is setup, and it may not be set up correctly here. @asmeurer @gforsyth and @CJ-Wright might have a better answer to that question.

[CJ-Wright]

I think doctr knows if it is building on the master branch and doesn't push unless it is on the master branch, unless you have some special settings.
You could just test this by putting up a trial PR and see if it shows up on the webpage.

[asmeurer]

doctr only pushes from master unless --no-require-master is used (it isn't being used in this repo), and even then, it is impossible to push from a pull request from a fork.

[asmeurer]

And yes, in a PR, doctr runs all the steps of the deploy sans the push in every build to ensure that they would work. But the push is not done (see https://travis-ci.org/cyclus/rickshaw/builds/347951348#L1373). It seems we need to color the doctr output better.