From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: kbd@lists.altlinux.org
Subject: [kbd] [PATCH] docs/man/man5: Fix warnings from "groff"
Date: Fri, 20 Mar 2020 19:07:35 +0000 [thread overview]
Message-ID: <20200320190734.GA27944@rhi.hi.is> (raw)
Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z
[ "test-groff" is a developmental version of "groff" ]
Input file is ./docs/man/man5/keymaps.5
<docs/man/man5/keymaps.5>:81 (macro BI): only 1 argument, but more are expected
<docs/man/man5/keymaps.5>:94 (macro BI): only 1 argument, but more are expected
<docs/man/man5/keymaps.5>:336 (macro BI): only 0 argument, but more are expected
an-end-check:<docs/man/man5/keymaps.5>: Warning: Different number of .RS and .RE calls, an-RS-open=1 at end of file
Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
docs/man/man5/keymaps.5 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/man/man5/keymaps.5 b/docs/man/man5/keymaps.5
index 4d9fe52..82d5903 100644
--- a/docs/man/man5/keymaps.5
+++ b/docs/man/man5/keymaps.5
@@ -78,7 +78,7 @@ represent keyboard actions, of which up to 256 can be bound to a single
key. The actions available include outputting character codes or
character sequences, switching consoles or keymaps, booting the machine
etc. (The complete list can be obtained from dumpkeys(1) by saying
-.BI " dumpkeys -l"
+.B " dumpkeys -l"
\&.)
.LP
Each
@@ -91,7 +91,7 @@ If Shift+CapsLock should not produce a lower case symbol, put lines like
.LP
.RS
.nf
-.BI "keycode 30 = +a A"
+.B "keycode 30 = +a A"
.fi
.RE
.LP
@@ -333,8 +333,7 @@ key action code sends. The syntax of string definitions is:
.B string
.I keysym
.B =
-.BI
-"text"
+.BI """" text """"
.RE
.LP
.I text
@@ -429,6 +428,7 @@ the "spare" action code F100 not normally bound to any key.
.nf
altgr keycode 32 = F100
string F100 = "du\\ndf\\n"
+.RE
.LP
.SH "SEE ALSO"
.BR loadkeys (1),
--
2.25.1
reply other threads:[~2020-03-20 19:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200320190734.GA27944@rhi.hi.is \
--to=bjarniig@rhi.hi.is \
--cc=kbd@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).