We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found a bug that is very easy to reproduce.
Write the following to the config (book.toml):
book.toml
[book] src="../"
And then run, for example, mdbook build:
mdbook build
C:\Users\{path-to-the-book}>mdbook build 2022-02-21 18:00:53 [INFO] (mdbook::book): Book building has started 2022-02-21 18:00:53 [INFO] (mdbook::book): Running the html backend 2022-02-21 18:00:54 [ERROR] (mdbook::utils): Error: Rendering failed 2022-02-21 18:00:54 [ERROR] (mdbook::utils): Caused By: Failed to read "C:\\Users\\{path-to-the-book}\\../mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\mdbook\\book\\FontAwesome\\fonts\\fontawesome-webfont.eot" 2022-02-21 18:00:54 [ERROR] (mdbook::utils): Caused By: {System cannot find the path [written in my native language]} (os error 3)
File tree view: it recursively creates and fills several books:
If this is indeed a bug, can I bypass it somehow? I want to build a book with root located in the directory above the book (../).
../
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I found a bug that is very easy to reproduce.
Write the following to the config (
book.toml
):And then run, for example,
mdbook build
:File tree view: it recursively creates and fills several books:

If this is indeed a bug, can I bypass it somehow? I want to build a book with root located in the directory above the book (
../
).The text was updated successfully, but these errors were encountered: