linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Ingo Schwarze <schwarze@usta.de>
Cc: linux-man@vger.kernel.org, groff@gnu.org
Subject: linting mdoc(7) pages (was: [PATCH v2] man*/: ffix (migrate to `MR`))
Date: Wed, 16 Aug 2023 23:57:33 +0200	[thread overview]
Message-ID: <d1792e49-5432-bcb7-5eb0-97ab26e8700f@kernel.org> (raw)
In-Reply-To: <0868892e-3c5e-c6ae-f0a7-bfd9b08987c6@kernel.org>


[-- Attachment #1.1: Type: text/plain, Size: 2795 bytes --]

Hi Ingo!

On 2023-08-16 20:25, Alejandro Colomar wrote:
> Hi Ingo!
> 
> On 2023-08-16 18:33, Ingo Schwarze wrote:
>> That perspective is not really helpful for general purpose Linux
>> distributions: for these, the Linux man-pages project matters a lot,
>> and that project is not considering the man(7) language as obsolete at
>> all.  That i keep recommending changing that stance does not appear to
>> have much effect so far
> 
> It does have an effect, or I like to think it has.  Branden and I are
> pushing to improve man(7) to be on par with mdoc(7) where it's lacking.
> 
> I also recently added support for mdoc(7) in the build system, so new
> mdoc(7) pages will enjoy the same linting level to which I subject our
> existing man(7) pages.  If anyone wants to write new pages using
> mdoc(7), they're welcome.  I'm not going to require man(7) (but I
> prefer it for my own pages).
> 
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/share/mk?id=c76a587148d9b69667852311ece53403b1458844>
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/share/mk?id=5a34548ecbf4200b4a7bcc3ce9f26bedd84450cb>
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/share/mk?id=3c8198d1786501eb4a9e9a46c61c17ff233f3d54>
> 
> So, if anyone wants to add a page that's not present, and decides to
> write it using mdoc(7), it'll be welcome.  That includes the suggestion
> of a new intro.1, which IIRC was written in mdoc(7).  I should revise
> that page.  I lack experience using it, but I guess I'll learn more
> with enough time.
> 
> Also, if anyone wants to fork this project and rewrite it using mdoc(7),
> or maybe use it for having a documentation repo of whatever project,
> I made it easy to do so.  (In fact, I added mdoc(7) support for linting
> an mdoc(7) page at my job.)
> 
> I even plan to add support for mm(7) pages, if POSIX deigns to talk to
> me to provide their sources.

BTW, I remember you showed interest in the ability to lint all pages.
You may be interested in trying this:

$ make lint-mdoc MANDIR=/home/alx/src/bsd/openbsd/src -k

You may really use anything as MANDIR, and you may also use different
targets, but lint-mdoc will run mandoc(1) as the linter, which I guess is
the most interesting one to you.  Check `make help` for that.

You may need to adjust a few command variables to use the gnu variants,
as I doubt I write portable stuff.  Ye be warned.  Check
`make help-variables` for that.

If you try this, you'll need the very latest commit, as I just fixed
a bug in a script that misinterpreted some pathname in the OpenBSD tree.

Cheers,
Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-08-16 21:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 17:52 [PATCH v2] man*/: ffix (migrate to `MR`) G. Branden Robinson
2023-07-31 21:47 ` Alejandro Colomar
2023-07-31 22:50   ` G. Branden Robinson
2023-07-31 23:15     ` Alejandro Colomar
2023-08-01 20:10       ` G. Branden Robinson
2023-08-17  0:14         ` Brian Inglis
2023-07-31 22:16 ` Jakub Wilk
2023-07-31 23:30   ` Alejandro Colomar
2023-08-01  1:31   ` G. Branden Robinson
2023-08-01 13:35     ` Alejandro Colomar
2023-08-01 14:12       ` G. Branden Robinson
2023-08-12 15:35         ` Alejandro Colomar
2023-08-16  3:55           ` G. Branden Robinson
2023-08-16 12:12             ` Alejandro Colomar
2023-08-16 16:33             ` Ingo Schwarze
2023-08-16 18:25               ` Alejandro Colomar
2023-08-16 21:57                 ` Alejandro Colomar [this message]

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=d1792e49-5432-bcb7-5eb0-97ab26e8700f@kernel.org \
    --to=alx@kernel.org \
    --cc=groff@gnu.org \
    --cc=linux-man@vger.kernel.org \
    --cc=schwarze@usta.de \
    /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).