Status: Accepted
Owner: percival.music.ca
Labels: Type-Enhancement Priority-Medium Maintainability
New issue 867 by percival.music.ca: lilypond-book can have hash collisions
http://code.google.com/p/lilypond/issues/detail?id=867
It would be nice if lilypond-book checked if a filename already exists in
def write_ly (self)
and took some action. Currently, if there's a hash collision (either from
pure fluke of an actual hash collision, or much more likely, the same
snippet being included multiple times) it just blindly overwrites the old
file.
This could theoretically be a problem for a user, but it's much more likely
to annoy the doc build.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
