Re: -column issue

[Kristaps Dzonsons <kristaps@bsd.lv>]

[-- Attachment #1: Type: text/plain, Size: 1479 bytes --]

Jason McIntyre wrote:
> 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).

Jason, I can't replicate this.  Enclosed is the input (so as to preserve 
the tabbing...).  I tested with OpenBSD and a new groff.  Do you still 
see this behaviour?

Kristaps

[-- Attachment #2: foo.1 --]
[-- Type: text/plain, Size: 219 bytes --]

.Dd $Mdocdate$
.Dt FOO 1
.Os
.Sh NAME
.Nm foo
.Nd bar
.Sh DESCRIPTION
.Bl -column "Second level nameXXXXXX" integerXXX -offset indent
.It Sy Second level name	Type	Changeable
.It Dv FS_POSIX_SETUID No 	integer	yes 
.El