Hi Helge, At 2023-01-22T20:31:25+0100, Helge Kreutzmann wrote: > Without further ado, the following was found: > > Issue: Why hard (and strange) line breaks? > > "Since, when one uses\n" [...] I don't see these "\n" line endings in Git HEAD or the change history of the page. Maybe there is a problem with your searching/reporting tool? I would add that these are not "hard line breaks" in the *roff language. "\n" is the register interpolation escape sequence. It must always be followed by an argument, the name of the register to be interpolated. Register interpolation should not be used in portable man pages. But I don't think it's happening here. groff 1.22.4 (and earlier) diagnose the incorrect input as follows. $ printf 'hello\\n\n' | nroff | cat -s troff: <standard input>:1: a newline character is not allowed in an escape name hello groff 1.23.0 will be a little more precise. (The escape _name_ itself is not where the invalid syntax was encountered.) $ printf 'hello\\n\n' | ./build/test-groff -T utf8 | cat -s troff:<standard input>:1: error: a newline character is not allowed in an escape sequence parameter hello In any event, "git blame" says the following about the relevant portion of the page. a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1009) Since, when one uses a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1010) .BR unshare (1) a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1011) to create a mount namespace, 8c9a827429 (Michael Kerrisk 2021-08-18 01:34:54 +0200 1012) the goal is commonly to provide full isolation of the mounts a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1013) in the new namespace, a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1014) .BR unshare (1) a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1015) (since 1ae6b2c7b8 (Alejandro Colomar 2022-03-18 20:25:09 +0100 1016) .I util\-linux b324e17d32 (Alejandro Colomar 2022-12-04 20:38:06 +0100 1017) 2.27) in turn reverses the step performed by a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1018) .BR systemd (1), 8c9a827429 (Michael Kerrisk 2021-08-18 01:34:54 +0200 1019) by making all mounts private in the new namespace. a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1020) That is, a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1021) .BR unshare (1) a66648bbd1 (Michael Kerrisk 2021-08-17 05:04:11 +0200 1022) performs the equivalent of the following in the new mount namespace: That is why I suspect a problem with your tool. Regards, Branden
Attachment:
signature.asc
Description: PGP signature
