-
Notifications
You must be signed in to change notification settings - Fork 111
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
Support dashes in default.extend-identifiers
#646
Comments
Maybe the solution in #575 works here as well |
I've updated the docs with the definition of an identifier (uncode XID_Continue) and word (split identifier). Yes, these are cases where identifiers are split by a dash. The challenge is knowing when to treat them as identifiers or not and how to do so efficiently. |
I don't think so: in #575, @epage suggests using
Thank you for this! While being correct, I find the unicode reference hard to read and to derive common cases from. For example, within 5 minutes, I wasn't able to find that a dash separates two identifiers. What do you think about #648?
Generally, dashes split identifiers, right? In that case, and if it stays this way, we can close this issue with #648 imo. |
Duplicates: #400. |
Thank you for
typos
, this is an amazing app!I'd like to be able to have identifiers with dashes in
default.extend-identifiers
. I need it for gcc's-Wno-hsa
and clang-tidy'sclang-analyzer-optin
. (Note: Bare keys with dashes are supported by toml)Does a dash separate two identifiers or is it part of one identifier, similar to an underscore? Should we add this info to the docs? I can't find this anywhere.
Minimal example:
.typos.toml
:example.txt
:The text was updated successfully, but these errors were encountered: