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

Some more fixes for building docs #914

Merged
merged 6 commits into from
Dec 11, 2016
Merged

Some more fixes for building docs #914

merged 6 commits into from
Dec 11, 2016

Conversation

lucc
Copy link
Collaborator

@lucc lucc commented Dec 11, 2016

Sorry there where quite some things I overlooked in #912.

`sphinx-build -W` was complaining as this is not a option of alot and can not
be found in our documentation.
The path to the present development version of alot should be prepended to
sys.path in order to shadow other versions of alot installed on the system.
Also it should be a directory from which the alot module is loadable.  That is
the root of the git repository and not one level above this.

This was overlooked in pazz#912.
When checking out files from git the timestamps might not give enough
information to make which files to remake.  So this new target can be used to
force a remake of all generated files on the next run.
@@ -47,7 +57,7 @@

where to store outgoing mails, e.g. `maildir:///home/you/mail/Sent`.
You can use mbox, maildir, mh, babyl and mmdf in the protocol part of the URL.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick: should we try to avoid these trailing whitespaces to be introduced?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Copy link
Owner

@pazz pazz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These look good to me.
(I'd rather OK every commit individually but I don't see how to do this..)

@lucc
Copy link
Collaborator Author

lucc commented Dec 11, 2016

I used two different approaches to remove the trailing ws from the autogen. docs. Do you think this is ok or would you prefer to remove trailing ws in the second script as well (I think that might be a bit more difficult as with the first script).

@lucc
Copy link
Collaborator Author

lucc commented Dec 11, 2016

Also NB: The "Changes approved" mark from your review was not removed by github even though I pushed new commits.

@pazz
Copy link
Owner

pazz commented Dec 11, 2016

re reviews: yes, that's strange.. next time i'll simply hold back longer :)
I think the current way of dealing with trailing spaces is ok. Its not the end of the world anyway if one sneaks in after all..

@pazz pazz merged commit 639bd05 into pazz:master Dec 11, 2016
@lucc lucc deleted the docs2 branch December 11, 2016 20:17
ryneeverett pushed a commit to ryneeverett/alot that referenced this pull request Mar 13, 2020
Some more fixes for building docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants