From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: Opinions on .Dd?
Date: Mon, 26 Jul 2010 16:06:22 +0100 [thread overview]
Message-ID: <20100726150646.GE24722@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4C4DA22A.9020905@bsd.lv>
On Mon, Jul 26, 2010 at 04:56:42PM +0200, Kristaps Dzonsons wrote:
>
> % cat foo.3
> .Dd
> .Dt FOO 1
> .Os
> .Sh NAME
> .Nm foo
> .Nd bar
> .Sh DESCRIPTION
> Moo.
> % nroff -mandoc foo.3
> FOO(1) BSD General Commands Manual FOO(1)
>
> NAME
> foo - bar
>
> DESCRIPTION
> Moo.
>
> BSD Epoch BSD
>
> (Note groff output chopped, as they don't have our awesome -Owidth
> argument.) This is on GNU/Linux (groff 1.18.1). I also tested on
> OpenBSD and NetBSD. Same.
>
ah. i like it!
> If you enter an invalid string, say, `.Dd urgle', then you get the
> current date.
>
ah, ok. just w/o args gets you Epoch. i was confused because i thought
you were trying to say that Dd did not accept arguments.
> > even so, i think it would be great to print "Epoch". there is no
> > difference between "Epoch" and "", except a little humour.
>
> I actually think it's a bug.
>
well, it's a great one. please don;t remove it. "Epoch" is exactly the
correct thing to do.
> What I was getting at, regarding (e.g.) DFBSD and what to put in the
> `Dd' field, is maybe they're best off leaving it blank.
>
i don;t see the point of that. a ton of work to make things less useful.
> >
> > this ties in with how do we handle OS differences... different pages, or
> > a single page which notes differences. the latter might seem sane, but
> > it could make the page unwieldy.
>
> Single page, I think. Are there really so many differences?
>
my previous mail listed some between netbsd and openbsd. there are
probably not too many, i think, but that doesn;t mean there won;t be
more. single page is the easiest way to go for sure. but like, will
freebsd dudes want a list of openbsd's differences in their man page(s)?
and vice versa?
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-07-26 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-25 4:30 Sascha Wildner
2010-07-25 6:25 ` Ingo Schwarze
2010-07-25 12:08 ` Sascha Wildner
2010-07-26 13:42 ` Kristaps Dzonsons
2010-07-26 14:50 ` Jason McIntyre
2010-07-26 14:56 ` Kristaps Dzonsons
2010-07-26 15:06 ` Jason McIntyre [this message]
2010-07-25 8:37 ` Jason McIntyre
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=20100726150646.GE24722@bramka.kerhand.co.uk \
--to=jmc@kerhand.co.uk \
--cc=discuss@mdocml.bsd.lv \
/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).