From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Re: -column issue
Date: Fri, 6 Aug 2010 18:51:36 +0059 [thread overview]
Message-ID: <20100806175200.GB946@bramka.kerhand.co.uk> (raw)
In-Reply-To: <4C5C417B.4050209@bsd.lv>
On Fri, Aug 06, 2010 at 07:08:11PM +0200, Kristaps Dzonsons wrote:
> >hi. there's a formatting issue for -column lists. the best example i can
> >find is in openbsd's sysctl.3 (it's riddled with these):
> >
> > .Bl -column "Second level nameXXXXXX" integerXXX -offset indent
> > .It Sy Second level name Type Changeable
> > .It Dv FS_POSIX_SETUID No " integer yes"
> > .El
>
> UGH. This is gross. Why why why didn't they do:
>
> 46 .Bl -column "Second level nameXXXXXX" integerXXX -offset indent
> 47 .It Sy Second level name Type Changeable
> 48 .It Dv FS_POSIX_SETUID No integer yes
>
> (With tabs between columns.) It renders just fine in both mandoc and
> new/old groff.
>
"they" didn;t do it, presumably, because whichever poor bastard wrote it
probably just jiggled the list until it formatted correctly. that is
roughly how one goes about constructing a -column list.
anyway, are you sure that your solution is correct? look carefully at how
groff formats it:
Second level name Type Changeable
FS_POSIX_SETUID No integer yes
i.e. it does not parse "No". mandoc does not display the "No". same if i
move the "No" into the next column (which seems more logical).
jmc
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-08-06 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 7:06 Jason McIntyre
2010-08-06 17:08 ` Kristaps Dzonsons
2010-08-06 17:52 ` Jason McIntyre [this message]
2010-08-06 18:13 ` Kristaps Dzonsons
2010-08-06 18:23 ` Jason McIntyre
2010-08-06 18:35 ` Kristaps Dzonsons
2010-08-07 16:15 ` Ingo Schwarze
2010-08-07 15:59 ` Ingo Schwarze
2010-08-07 17:32 ` Kristaps Dzonsons
2010-08-07 18:03 ` 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=20100806175200.GB946@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).