From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 59631@debbugs.gnu.org
Subject: bug#59631: 29.0.50; [PATCH] New check-man target to check man pages for errors
Date: Sat, 03 Dec 2022 16:39:02 +0200 [thread overview]
Message-ID: <5D781E9D-7C4E-45A9-A289-F8DBF7782034@gnu.org> (raw)
In-Reply-To: <CADwFkmnNJ6WwXnUfhYgX3wiMP5-HDNvF04jQqaJ2Q_LT0u4ZZg@mail.gmail.com>
On December 3, 2022 4:20:50 PM GMT+02:00, Stefan Kangas <stefankangas@gmail.com> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > AFAICT, the pipeline is simple:
> >
> > soelim FILE | preconv -e UTF-8 | groff -mandoc -Z -wall -wmac -Tutf8 > /dev/null
>
> My concern is that the command is more brittle in the face of changes,
> and also all the extra "echo" stuff that man-db is doing (probably
> because I don't understand what it's doing).
>
> I'm thinking that we could provide the above in case man-db isn't
> available. Is there any way to auto-detect that? If not, how about
> putting this behind a flag?
>
Nah, just install your variant. It isn't worth the hassle to do anything more complex. I have the command in my notes and will use it if and when required.
next prev parent reply other threads:[~2022-12-03 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 15:23 bug#59631: 29.0.50; [PATCH] New check-man target to check man pages for errors Stefan Kangas
2022-11-27 15:44 ` Eli Zaretskii
2022-11-27 17:49 ` Stefan Kangas
2022-11-27 18:15 ` Eli Zaretskii
2022-11-27 22:59 ` Stefan Kangas
2022-11-28 12:13 ` Eli Zaretskii
2022-12-01 15:02 ` Stefan Kangas
2022-12-01 16:01 ` Eli Zaretskii
2022-12-02 22:50 ` Richard Stallman
2022-12-03 7:06 ` Eli Zaretskii
2022-12-03 14:20 ` Stefan Kangas
2022-12-03 14:39 ` Eli Zaretskii [this message]
2022-12-09 10:25 ` Stefan Kangas
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=5D781E9D-7C4E-45A9-A289-F8DBF7782034@gnu.org \
--to=eliz@gnu.org \
--cc=59631@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.