all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: 59631@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#59631: 29.0.50; [PATCH] New check-man target to check man pages for errors
Date: Sat, 03 Dec 2022 09:06:35 +0200	[thread overview]
Message-ID: <83mt85dkzo.fsf@gnu.org> (raw)
In-Reply-To: <E1p1Er7-0001oV-L1@fencepost.gnu.org> (message from Richard Stallman on Fri, 02 Dec 2022 17:50:05 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: stefankangas@gmail.com, 59631@debbugs.gnu.org
> Date: Fri, 02 Dec 2022 17:50:05 -0500
> 
> A feature limited to GNU-Like systems is not a horrible thing.  Our
> policy is that support for non-GNU-like systems is at best a secondary
> goal -- something users can implement if they wish, but we don't
> consider the lack of that support as a problem.
> 
> It's fine to make this call Groff directly, if it has no major
> drawbacks.  But please don't imply that the absence of that support
> would be horrible.

This is not a user-level feature.  This is a feature for Emacs developers,
and only for those of them who routinely work on producing the release
tarballs.  From my POV, it is important to make this kind of features to
work on as many systems as possible, if only to allow me to do these jobs
from my local system.

The feature is implemented in Groff, btw, the man page of 'man' says that
explicitly.

And I didn't say the inability to use Groff directly would be "horrible",
quite the contrary.  Quote:

> 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.

Note the last paragraph.

So I consider your reprimand gratuitous and even mildly insulting.  It
sounds like you reacted to a single sentence, taken out of context, and
either didn't read or forgot the other messages I wrote in this thread.





  reply	other threads:[~2022-12-03  7:06 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 [this message]
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=83mt85dkzo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=59631@debbugs.gnu.org \
    --cc=rms@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.