From: "Paul A. Patience" <paul@apatience.com>
To: discuss@mandoc.bsd.lv
Subject: Spurious space in demandoc.1
Date: Sun, 13 Mar 2022 01:20:37 +0000 [thread overview]
Message-ID: <87o82aabvi.fsf@apatience.com> (raw)
Hi,
I found a typo in demandoc.1.
Not sure if it's worth a commit all by itself.
Best regards,
Paul
--- demandoc.1.bak 2022-03-12 20:11:41.670983926 -0500
+++ demandoc.1 2022-03-12 20:11:45.715031175 -0500
@@ -80,7 +80,7 @@
Such errors cause
.Nm
to exit at once, possibly in the middle of parsing or formatting a file.
-The output databases are corrupt and should be removed .
+The output databases are corrupt and should be removed.
.El
.Sh EXAMPLES
The traditional usage of
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2022-03-13 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 1:20 Paul A. Patience [this message]
2022-03-20 16:00 ` Ingo Schwarze
2022-03-20 16:05 ` Ingo Schwarze
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=87o82aabvi.fsf@apatience.com \
--to=paul@apatience.com \
--cc=discuss@mandoc.bsd.lv \
/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 NNTP newsgroup(s).