-
Notifications
You must be signed in to change notification settings - Fork 141
Open
Labels
A-tokenArea: tokenization, including definition of identifiers and wordsArea: tokenization, including definition of identifiers and wordsC-enhancementCategory: Raise on the bar on expectationsCategory: Raise on the bar on expectationsS-waiting-on-decisionStatus: Waiting on a go/no-go before implementingStatus: Waiting on a go/no-go before implementing
Description
And maybe it shouldn't, but I wanted to bring it up in case it hasn't been before:
Here's an example:
[......] they provide a standard way to include non-standard informa-
tion in the archive). If neither exists, the character will be a
hyphen (`-'); if there is an extended local header but no extra field,
`l'; if the reverse, `x'; and if both exist, `X'. Thus the file in
this example is (probably) a text file, is not encrypted, and has nei-
ther an extra field nor an extended local header associated with it.
What I'm wondering is, would it even be worth it to have an argument that says "respect wrapped hyphenated words"?
In this case that's information
and neither
.
Example for posterity:
error: `indicat` should be `indicate`
--> ./third_party/unzip/zipinfo.txt:153:71
|
153 | several values. The first character may be either `t' or `b', indicat-
| ^^^^^^^
Metadata
Metadata
Assignees
Labels
A-tokenArea: tokenization, including definition of identifiers and wordsArea: tokenization, including definition of identifiers and wordsC-enhancementCategory: Raise on the bar on expectationsCategory: Raise on the bar on expectationsS-waiting-on-decisionStatus: Waiting on a go/no-go before implementingStatus: Waiting on a go/no-go before implementing