-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Emacs lockfiles produce "Rendering failed" errors #2224
Comments
This seems very relevant: notify-rs/notify#255 The issue seems very hard to tackle. Very often, failing is what you want to do when your symlink is broken. Emacs is a rare special case. It seems like Emacs doesn't support other forms of lockfiles either, so I fear this is unfixable. I guess this could be better documented, or a flag might be added when |
@rustbot label +A-Documentation +C-dependency-bug +Command-serve +Command-watch +S-Blocked-Upstream |
Problem
When an Emacs buffer has been edited but not saved, Emacs generates a lock file in the form of a symlink to a nonexistent file. E.g., when editing
SUMMARY.md
:mdBook does not like these files:
Steps
SUMMARY.md
in Emacs and make a small edit, but do not save.mdbook build
.Expected:
Actual:
Possible Solution(s)
.#*.md
build
command (as well aswatch
,serve
, etc.) could (optionally?) ignore broken symlinks(N.b. I'm new to mdBook; it's possible these mechanisms exist and I'm just not finding them in the docs. In which case, it would be nice to surface them more prominently there.)
Notes
This isn't a showstopper as it's cleared up as soon as the file is saved (or in the event of a crash, as soon as the offending symlink is deleted). Still, it creates a lot of noise, particularly in
watch
orserve
mode, and makes it hard to see legitimate warnings/errors.Version
The text was updated successfully, but these errors were encountered: