Skip to content

book.toml Configuration file failure #1774

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

Closed
Week2019 opened this issue Mar 30, 2022 · 4 comments · Fixed by #1775
Closed

book.toml Configuration file failure #1774

Week2019 opened this issue Mar 30, 2022 · 4 comments · Fixed by #1775

Comments

@Week2019
Copy link

Week2019 commented Mar 30, 2022

Does v0.4.16 still read information from book.toml? When I switch from 0.4.15 to 0.4.16, all previous changes are scrapped. For example, the CSS file, the JS file and the no-section-label configuration items in book.toml are no longer functional.

@ehuss
Copy link
Contributor

ehuss commented Mar 30, 2022

Hm, that's a little worrisome. I can't reproduce the issue, though. I tried with a book.toml of:

[book]
title = "foo"

[output.html]
no-section-label = true

And the book rendered without the section labels.
Can you provide a more complete reproduction? Can you say more about exactly what you did?

@Week2019
Copy link
Author

Hm, that's a little worrisome. I can't reproduce the issue, though. I tried with a book.toml of:

[book]
title = "foo"

[output.html]
no-section-label = true

And the book rendered without the section labels. Can you provide a more complete reproduction? Can you say more about exactly what you did?

This is my profile

[book]
authors = []
language = "zh"
multilingual = false
src = "src"

[output.html]
no-section-label = true

[output.html.print]
enable = false

After my attempts, here is the problem

[output.html.print]
enable = false

This is the configuration I had in the previous version.

enable = false generated an error,disables most configurations, including no-section-label = true

@ehuss
Copy link
Contributor

ehuss commented Mar 30, 2022

Ah, apologies, I see what is wrong. I'll post a fix soon.

@ehuss
Copy link
Contributor

ehuss commented Mar 30, 2022

This should be fixed in v0.4.17, please let me know if you have any trouble with that version.

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 a pull request may close this issue.

2 participants