Re: [PATCH v2 2/2] sched_setattr.2: Document sched_util_{min,max}
From: Alejandro Colomar <alx@kernel.org>
Date: 2024-06-13 21:31:38
Hi Brian, On Thu, Jun 13, 2024 at 01:29:44PM GMT, Brian Norris wrote:
On Thu, Jun 13, 2024 at 12:15:55AM +0200, Alejandro Colomar wrote:quoted
On Wed, Jun 12, 2024 at 01:44:53PM GMT, Brian Norris wrote:quoted
+maximum frequency and is represented by a utilization value of +0.2 * 1024 = 205.This should go in italics. $ MANWIDTH=72 man man-pages | sed -n '/Expressions/,/^$/p' Expressions, if not written on a separate indented line, should be specified in italics. Again, the use of nonbreaking spaces may be appropriate if the expression is inlined with normal text.Regarding the nonbreaking spaces part: I'm not too practiced with groff, but the wording around the \[ti] character is confusing. AFAICT, I actually need to spell my expression like the following? 0.2\~*\~1024\~=\~205 At least, with trial and error, that's what appears to render correctly, whereas \[ti] renders as a literal tilde. Is man-pages.7 [1] incorrect? Brian [1] from `man man-pages`: "In this case, it may be worth using nonbreaking spaces (\[ti]) at suitable places in the command."
Yup; that's a bug. I introduced it by accident in
commit 36f73ba37945c7ff4aa2d8383f831519a38e3f27
Author: Alejandro Colomar [off-list ref]
Date: Sun Feb 5 22:59:22 2023 +0100
man-pages.7: Recommend using \[..] instead of \(.. escapes
They are more readable.
Signed-off-by: Alejandro Colomar [off-list ref]
Which did:
-(\e\(ti) at suitable places in the command.
+(\e[ti]) at suitable places in the command.
but it should have been (\e\[ti]). The intention was to render as (\~).
Would you mind sending a fix as part of your patch set?
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es/> Attachments
- signature.asc [application/pgp-signature] 833 bytes