all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Mon, 28 Nov 2022 14:13:29 +0200	[thread overview]
Message-ID: <83zgcbnuom.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnHvkid+A=Pf-T-x0KL5qhNKRED+bGWkpvr7r=QbX7KdA@mail.gmail.com> (message from Stefan Kangas on Sun, 27 Nov 2022 14:59:34 -0800)

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sun, 27 Nov 2022 14:59:34 -0800
> Cc: 59631@debbugs.gnu.org
> 
> I think adding it to make-tarball is a good idea.  Perhaps we could do
> it in the same step as checking the refcards?  I've attached a new patch
> with a suggested wording, please let me know what you think.

SGTM.

> I also enabled a few more groff warnings, and cleaned up the output to
> enable automatically jumping to errors from *compilation* buffers.

Can this be done by running Groff directly instead of via 'man'?  If it's
possible, it's IMO better, since Groff installations are more widespread
than the particular variant of 'man' you used in the script.  E.g., I think
the requirement for C.UTF-8 locale being available can be dropped in that
case.

But if doing so requires too much effort or research, feel free to install
what you have.

Thanks.





  reply	other threads:[~2022-11-28 12:13 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 [this message]
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
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=83zgcbnuom.fsf@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.