You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into this following the instructions in the Example section on the crates.io page:
$ ucd-generate property-bool /tmp/ucd-10.0.0 --include Hyphen,Dash,Quotation_Mark --chars
No such file or directory (os error 2)
I had to dig into the code to figure out what was going on. The missing file is emoji-data.txt.
I reproduced this behavior with both version 0.2.1 (cargo install) and current master (b56d7f3).
I would have expected:
The instruction on crates.io to not run into file-not-found errors. Maybe a first example that doesn't require emoji-data.txt?
A more discoverable instruction for downloading emoji-data.txt. Maybe an adapted version of the note in emoji_properties.rs in the Example section, along with some hints for when it's needed and which version to pick?
Path-related error messages to spell out the troublesome path. Maybe relative to <ucd-dir>?
If you like I could make a PR to spell out the relevant path in error messages?
The text was updated successfully, but these errors were encountered:
This commit improves the overall failure modes when I/O errors occur
while reading UCD data. In particular, the emoji-data.txt file is not
parse of the main UCD download, so we permit reading it to fail if it's
an I/O error.
Error messages should now include file paths.
FixesBurntSushi#9
I ran into this following the instructions in the Example section on the crates.io page:
I had to dig into the code to figure out what was going on. The missing file is
emoji-data.txt
.I reproduced this behavior with both version 0.2.1 (cargo install) and current master (b56d7f3).
I would have expected:
emoji-data.txt
?emoji-data.txt
. Maybe an adapted version of the note inemoji_properties.rs
in the Example section, along with some hints for when it's needed and which version to pick?<ucd-dir>
?If you like I could make a PR to spell out the relevant path in error messages?
The text was updated successfully, but these errors were encountered: