Git Attribute overrides examples - why are some linguist override examples prefixed with -?
#6248
-
|
Some example usages are prefixed with a minus sign. I'm not sure why this is. I couldn't find any explanation in the docs
tools/export_bom.py -linguist-detectable
# ↑ is this minus correct?
# or should there be no minus?
tools/export_bom.py linguist-detectableIf there is a difference between |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You're probably not looking in the right docs 😉. This is standard
So the
Yup. The former sets the attribute (documented just above the "Unset" mentioned above) and the latter unsets the attribute as detailed above. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the explanation! I didn't realise that unsetting was even an option in If I could make a suggestion, then I would have found it easier to understand with a slight rephrasing Use the `linguist-detectable` attribute to mark or unmark (by prefixing with `-`) paths as detectable:
```gitattributes
# mark any matching files as detectable
*.kicad_pcb linguist-detectable
*.sch linguist-detectable
# unmark a specific file as detectable
tools/export_bom.py -linguist-detectable
``` |
Beta Was this translation helpful? Give feedback.
You're probably not looking in the right docs 😉.
This is standard
.gitattributesnotation so you should be looking at that documentation. From the.gitattributesdocumentation:So the
-is correct. Linguist also supports a non-standard Linguist-specific approach oflinguist-detectable=falsebut we're discouraging this use in favour of the use people expect from their other.gitattributesusage.