-
Notifications
You must be signed in to change notification settings - Fork 346
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
[ close #3373 ] Implement the proposed feature #3384
Conversation
We can try render the user manual with our new HTML backend with |
415a012
to
dc30f65
Compare
@vlopezj say something? Just curious, what's your timezone? It's 4:48 a.m. here. |
CI passed! Yay! |
@ice1000 It looks good; but I'll look at it in more detail this afternoon (I'm in Europe/Stockholm).
Yes, this is the way to go. There are however two issues that make it non-straightforward:
|
Note that we could push the generated html to github and have it sit at |
It shouldn't be a big problem to put the code-rendered rst files into the repo. It's possible to let Travis CI do this (although I don't know how to let Travis CI push commits into a repo without using a GitHub password). Why do we need to do it for each commit? Do you mean each commit since the very beginning or from now on? |
@@ -20,8 +20,7 @@ highlightOnlyCode HighlightAll _ = False | |||
highlightOnlyCode HighlightCode _ = True | |||
highlightOnlyCode HighlightAuto AgdaFileType = False | |||
highlightOnlyCode HighlightAuto MdFileType = True | |||
-- TODO: see #3373 | |||
highlightOnlyCode HighlightAuto RstFileType = False | |||
highlightOnlyCode HighlightAuto RstFileType = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The functions highlightOnlyCode
and highlightedFileExt
are specific to the HTML backend. They should go in Agda.Interaction.Highlighting.HTML
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure! I thought it'll be used somewhere else when I first impl these but seems not.
As @gallais pointed out, it seems we are already doing essentially the same thing for the Agda standard library (generating HTML files from Agda and pushing them to github pages). For the user manual, we have two steps: generating It seems that this can be done with Travis. To avoid the need for a Github password, I think you can generate some form of token, give it to Travis, and then reference it from the https://github.com/agda/agda-stdlib/blob/master/.travis.yml If we have this, I think it will be easier to bypass read the docs completely and just publish HTML files directly under https://agda.github.io/docs . @ice1000 In any case, the first step would be to have a Makefile rule (such as |
IMO It's a separated task. I like this idea but I'm not gonma do that in this PR. |
Makes sense. Then it looks ready for merging (apart from the comment about |
dc30f65
to
94b57ac
Compare
Signed-off-by: ice1000 <ice1000kotlin@foxmail.com>
…ight=auto` Signed-off-by: ice1000 <ice1000kotlin@foxmail.com>
Signed-off-by: ice1000 <ice1000kotlin@foxmail.com>
94b57ac
to
8359a8d
Compare
@vlopezj Rebased on master, Added changelog, documentation and addressed your comment. Please take a look. |
Signed-off-by: ice1000 ice1000kotlin@foxmail.com
Everything has already been covered in #3373