From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: Re: Fn issue
Date: Fri, 29 Oct 2010 15:07:22 +0200 [thread overview]
Message-ID: <20101029130722.GD8651@iris.usta.de> (raw)
In-Reply-To: <20101029124857.GB13301@kerhand.co.uk>
Hi Jason,
Jason McIntyre wrote on Fri, Oct 29, 2010 at 01:48:33PM +0100:
> hi. not sure if this is known or not (can;t see anything in the list
> that suggests it is).
I remember having seen that issue, but apparently neglected to list it.
> source, from rpc.3:
>
> .Ft int
> .Fn callrpc "char *host" "u_long prognum" "u_long versnum" "u_long procnum" "xdr proc_t inproc" "char *in" "xdrproc_t outproc" "char *out"
>
> groff:
> int
> callrpc(char *host, u_long prognum, u_long versnum, u_long procnum,
> xdrproc_t inproc, char *in, xdrproc_t outproc, char *out);
>
> mandoc:
> int
> callrpc(char *host, u_long prognum, u_long versnum, u_long procnum,
> xdrproc_t inproc, char *in, xdrproc_t outproc, char *out);
>
> i think the indentation in the groff formatting is nicer.
Indeed.
I have now added it to the list.
Thanks,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-10-29 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:48 Jason McIntyre
2010-10-29 13:07 ` Ingo Schwarze [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=20101029130722.GD8651@iris.usta.de \
--to=schwarze@usta.de \
--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).