mirror of
https://github.com/sharkdp/bat.git
synced 2025-01-15 01:58:23 +01:00
Add note on subdirectory's irrelevance to ordering
This commit is contained in:
parent
9f36a7a284
commit
c0f2d6f934
@ -100,14 +100,16 @@ like this:
|
|||||||
|
|
||||||
## Ordering
|
## Ordering
|
||||||
|
|
||||||
At compile time, all TOML files are processed in lexicographical filename order.
|
At compile time, all TOML files applicable to the target are processed in
|
||||||
So `00-foo.toml` takes precedence over `10-bar.toml`, which takes precedence
|
lexicographical filename order. So `00-foo.toml` takes precedence over
|
||||||
over `20-baz.toml`, and so on. This may be occasionally useful for creating
|
`10-bar.toml`, which takes precedence over `20-baz.toml`, and so on. Note that
|
||||||
high/low priority rules, such as in the aforementioned example of explicitly
|
**only** the filenames of the TOML files are taken into account; the
|
||||||
mapping `*.conf` files to unknown.
|
subdirectories they are placed in have no influence on ordering.
|
||||||
|
|
||||||
Generally this should not be much of a concern, since rules should be written as
|
This behaviour can be occasionally useful for creating high/low priority rules,
|
||||||
specifically as possible for each application.
|
such as in the aforementioned example of explicitly mapping `*.conf` files to
|
||||||
|
unknown. Generally this should not be much of a concern though, since rules
|
||||||
|
should be written as specifically as possible for each application.
|
||||||
|
|
||||||
Rules within each TOML file are processed (and therefore matched) in the order
|
Rules within each TOML file are processed (and therefore matched) in the order
|
||||||
in which they are defined. At runtime, the syntax selection algorithm will
|
in which they are defined. At runtime, the syntax selection algorithm will
|
||||||
|
Loading…
Reference in New Issue
Block a user