Skip to content
Novus Examples
conf77 B

Code Config — Editorconfig Snippet

Tiny SAMPLE tooling config snippet (editorconfig-snippet) for editor/linter harnesses.

Preview — first 7 linesconf
root = true

[*]
indent_style = space
indent_size = 2
end_of_line = lf

Specifications

Role
tooling-config
Wave
I

What is a .conf file?

A .conf text file here is an OpenSSH-style client configuration SAMPLE with Host stanzas for fictional hosts.

How to use this file

Use the SAMPLE SSH config to test SSH config parsers and StrictHostKeyChecking tooling without real host keys.

How to use this file for testing

“Code Config — Editorconfig Snippet” is a deterministic Novus Examples fixture for Config parsing, Editor testing, Code parsing. TOML and INI configuration files with nested sections and typed values — for testing config parsers and loaders.

Documented properties for this file: tooling-config. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

This is a short, known-correct source file. Run it through your syntax highlighter, linter, formatter, tree-sitter grammar, or parser, and open it in the in-browser editor to tweak and re-download. Each snippet exercises comments, string escapes, literals, and language keywords.

Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.

Generated by generation/pad_wave_i.py. Free for any use, no attribution required — license.