From: Thomas Klausner <wiz@NetBSD.org>
To: discuss@mdocml.bsd.lv
Subject: groff-1.19.2 difference: indent
Date: Sun, 18 Sep 2011 18:24:40 +0200 [thread overview]
Message-ID: <20110918162440.GA10245@danbala.tuwien.ac.at> (raw)
Nicolas Joly reports a few differences between groff 1.19.2 and
1.11.1.
I've verified against 1.11.7, only one of them is still there:
----- Forwarded message from Nicolas Joly <njoly@pasteur.fr> -----
2) In SYNOPSIS, functions with big prototypes are not indented after
line wrap, which can occur between argument type and name. Check
wborder(3).
20,21c20,21
< wborder(WINDOW *win, chtype ls, chtype rs, chtype ts, chtype bs,
< chtype tl, chtype tr, chtype bl, chtype br);
---
> wborder(WINDOW *win, chtype ls, chtype rs, chtype ts, chtype bs, chtype
> tl, chtype tr, chtype bl, chtype br);
----- End forwarded message -----
Additionally, I've also noticed on this example that "chtype" and "tl"
are split across lines. The source for this is:
.Fa "chtype tl"
I wonder why it's split and not handled as one item?
Cheers,
Thomas
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next reply other threads:[~2011-09-18 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 16:24 Thomas Klausner [this message]
2011-09-18 16:32 ` Ingo Schwarze
2011-09-19 13:35 ` Thomas Klausner
2011-09-20 9:12 ` Ingo Schwarze
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=20110918162440.GA10245@danbala.tuwien.ac.at \
--to=wiz@netbsd.org \
--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).