Description
Inspect a default-tab Makefile recipe prefix.
Build and configuration formats have dialect-specific quoting, whitespace and escaping rules. A local prefix or character transformation handles only the declared fragment, leaving full parsing, evaluation and precedence to the consuming implementation.
Inspect a default-tab Makefile recipe prefix.
When to use this tool
Use Makefile Recipe Tab Prefix when inspecting the stated text or configuration fragment.
How to use the tool and how it works
- Enter line. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read recipe, body. Inspect recipe before interpreting the associated values.
Inspect a default-tab Makefile recipe prefix. recipe is true only when line begins with a tab; body removes exactly that first tab or returns the original line.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| line | Line | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| recipe | Recipe | Required. Boolean. |
| body | Body | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"line": "\techo hello"
},
"output": {
"recipe": true,
"body": "echo hello"
}
}Limitations and assumptions
- Custom recipe prefixes, continuations and complete Makefile parsing are not supported.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the appropriate full parser and actual configuration context for reliable interpretation or application.
References
Similar or alternative tools
- Ninja Variable Dollar Escape
Escape literal dollar signs for a Ninja-style text fragment.
- Ini Section Leading Trailing Space Rule
Parse a single INI section header under an explicit trim rule.