15 lines
839 B
Markdown
15 lines
839 B
Markdown
# Search and investigation
|
|
|
|
Trace load order before treating a negative search as evidence of absence. Follow
|
|
includes, imports, sources, require/dofile calls, symlinks and generated outputs
|
|
within the assigned boundary. Identify which file is actually loaded and whether
|
|
a generator or package default supplies its value.
|
|
|
|
Search interpreted configuration for literal values and expression pieces:
|
|
modifier variables (mainMod, modKey, mod, leader), key or path fragments, function
|
|
and dispatcher names, modes, section names and visible outcomes. For example,
|
|
a binding may join mainMod with " + S" rather than contain "SUPER + S".
|
|
Combine alternatives in one broad search where the assigned search tool supports
|
|
it. When results are empty, check the search method, load order and admitted scope
|
|
before concluding the behavior is missing.
|