Hi Ingo,
this is a minimalized manpage that currently fails mandoc -Tlint:
.Dd November 8, 2017
.Dt AUDIO 3
.Os
.Sh NAME
.Nm libaudio
.Nd manipulate digital audio formats and files
.Sh SYNOPSIS
.In audio.h
.Ft AUFILE*
.Fn au_open "const char* path" "AUMODE mode" "AUINFO* info"
.Ft int
.Fn au_close "AUFILE* file"
.Sh DESCRIPTION
.Nm
provides a simple uniform interface to manipulating
digital audio data in various formats and file types.
.Sh RETURN VALUES
.Fn au_open
returns a pointer to an initialized
.Ft AUFILE
structure, or NULL if an error occurs.
.Fn au_close
returns 0 upon successfully closing the file,
or -1 if an error occurs.
$ mandoc -Tlint /tmp/libaudio.3
mandoc: /tmp/libaudio.3:1:5: STYLE: Mdocdate missing: Dd November (OpenBSD)
mandoc: /tmp/libaudio.3: STYLE: RCS id missing: (OpenBSD)
I remember this was not the case. Is it considered bad style if
a manpage does not have "$Mdocdate: ... $" and a RCS id such as
.\" $OpenBSD: ls.1,v 1.79 2016/10/24 13:46:58 schwarze Exp $ ?
I tried looking for this -Tlint change in cvsweb but could not find it.
This particular manpage is stored in git repo and does not have a RCS id.
In fact, it uses none of the $...$ constructs of CVS.
Is this enforced for base manpages, so that the OpenBSD mandoc requires it,
while the portable mandoc does not require it? I don't find it bad style
in general to not have a RCS id ...
Jan
