Open dmoles opened 8 months ago
This seems very relevant: https://github.com/notify-rs/notify/issues/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 notify-rs
lands support for ignoring symlink failures, but for now there's not much we can do.
@rustbot label +A-Documentation +C-dependency-bug +Command-serve +Command-watch +S-Blocked-Upstream
One way we could deal with this, as pointed out to me by @ehuss , would be to first put in a change resolving #1156/#1187 (such as PR #2183). Then, once that in place, all Emacs lockfiles can be specified via a pattern matching files starting with .#
in the mdbookignore
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