diff options
| author | Ingo Schwarze <schwarze@openbsd.org> | 2022-06-03 12:15:55 +0000 |
|---|---|---|
| committer | Ingo Schwarze <schwarze@openbsd.org> | 2022-06-03 12:15:55 +0000 |
| commit | f1a1415f2ac83d7454ab33bab918fe77f90664bd (patch) | |
| tree | cca4619f0ecb728de9a8697ed509838d8c4186bd /regress/roff/string/name.out_ascii | |
| parent | 4de2134e6e8bcf00651ea443b38238baef53467e (diff) | |
| download | mandoc-f1a1415f2ac83d7454ab33bab918fe77f90664bd.tar.gz | |
During identifier parsing, handle undefined escape sequences
in the same way as groff:
* \\ is always reduced to \
* \. is always reduced to .
* other undefined escape sequences are usually reduced to the escape name,
for example \G to G, except during the expansion of expanding escape
sequences having the standard argument form (in particular \* and \n),
in which case the backslash is preserved literally.
Yes, this is confusing indeed.
For example, the following have the same meaning:
* .ds \. and .ds . which is not the same as .ds \\.
* \*[\.] and \*[.] which is not the same as \*[\\.]
* .ds \G and .ds G which is not the same as .ds \\G
* \*[\G] and \*[\\G] which is not the same as \*[G] <- sic!
To feel less dirty, have a leaning toothpick, if you are so inclined.
This patch also slightly improves the string shown by the "escaped
character not allowed in a name" error message.
Diffstat (limited to 'regress/roff/string/name.out_ascii')
| -rw-r--r-- | regress/roff/string/name.out_ascii | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/regress/roff/string/name.out_ascii b/regress/roff/string/name.out_ascii index 325e28aa..38258a72 100644 --- a/regress/roff/string/name.out_ascii +++ b/regress/roff/string/name.out_ascii @@ -11,8 +11,12 @@ DDEESSCCRRIIPPTTIIOONN bs\\e: value of bs\\e bse: bs: + dot.: value of dot. + dot\.: value of dot. bl e: ble: bl: + inval\\G: value of inval\G + inval\G: value of inval\G -OpenBSD July 4, 2017 OpenBSD +OpenBSD June 3, 2022 OpenBSD |