Skip to content

Commit fa62d03

Browse files
committed
Merge branch 'db/doc-config-section-names-with-bs'
Doc update. * db/doc-config-section-names-with-bs: config.txt: document behavior of backslashes in subsections
2 parents 07b747d + 1feb061 commit fa62d03

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

Documentation/config.txt

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,13 @@ in the section header, like in the example below:
4141
--------
4242

4343
Subsection names are case sensitive and can contain any characters except
44-
newline (doublequote `"` and backslash can be included by escaping them
45-
as `\"` and `\\`, respectively). Section headers cannot span multiple
46-
lines. Variables may belong directly to a section or to a given subsection.
47-
You can have `[section]` if you have `[section "subsection"]`, but you
48-
don't need to.
44+
newline and the null byte. Doublequote `"` and backslash can be included
45+
by escaping them as `\"` and `\\`, respectively. Backslashes preceding
46+
other characters are dropped when reading; for example, `\t` is read as
47+
`t` and `\0` is read as `0` Section headers cannot span multiple lines.
48+
Variables may belong directly to a section or to a given subsection. You
49+
can have `[section]` if you have `[section "subsection"]`, but you don't
50+
need to.
4951

5052
There is also a deprecated `[section.subsection]` syntax. With this
5153
syntax, the subsection name is converted to lower-case and is also

0 commit comments

Comments
 (0)