mdbook uninstalls itself when running from a UNC file share
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.2k
- Forks
- 1.9k
- PR merge metrics
- PR metrics pending
Description
Problem
When running mdbook from a UNC file share and the command "mdbook serve --open" is used, mdbook will uninstall after a change is made. It will print "[INFO] (mdbook::book): Running the html backend" then exit. Running mdbook again will give the error "mdbook : The term 'mdbook' is not recognized... etc".
Steps
- Open an mdbook project in a UNC file share, e.g. \prod.mycompany.local\mynewguide
- Run "mdbook serve --open" in Powershell
- Make a change to a .md file
- After attempting to rebuild the book and run the html backend, mdbook will exit and uninstall itself from your machine
Possible Solution(s)
Copy the mdbook project to your local machine, do the required work, then copy back over to the file share.
Notes
No response
Version
mdbook v0.4.37
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing mdbook serve --open on a UNC file share in PowerShell, then trace the rebuild path after a .md change through the HTML backend. Done means the book rebuilds successfully and mdBook remains installed and runnable afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100