From 37eef3cf0ab0b0ed3dabc1c96515f4e30011f9db Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Tue, 6 Feb 2024 01:52:45 +0300 Subject: avoid Groff warnings due to `\` escapes * It's generally a bad idea to pass backslashes as a glyph in macro arguments, even as `\\` since this could easily be interpreted as an escape. * Instead we now always use `\[rs]`. --- doc/sciteco.7.template | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index cbfc512..4d4ed55 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -1630,7 +1630,7 @@ When \fB^V\fP is not followed by \fB^V\fP, a single character .BI ^W c Analogous to \fB^V\fP, but upper-cases characters. .TP -.SCITECO_TOPIC ^E\\ ^E\\q +.SCITECO_TOPIC ^E\[rs] ^E\[rs]q .BI ^E\(rs q Expands to the formatted number stored in the numeric part of Q-Register \fIq\fP. -- cgit v1.2.3