Bk -words badness

[Kristaps Dzonsons <kristaps@bsd.lv>]

Ingo, how goes the `Bk' work?  Scanning through mandoc's rendering of 
current manuals, I see a lot of the following sort of breakage:

.Bk -words
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
.Op Fl a Ar b
...

Which will, for obvious reasons, continue eternally past rmargin.

I have an intuition for how to implement an implied `Bk' for all 
SYNPRETTY blocks: to hook into print_mdoc_node() and set/unset the 
PREKEEP flag depending on the line number as reported in mdoc_node.

Would this sort of behaviour satisfy you?  The effect would be:

<PREKEEP>.Op Fl a Ar b<UNKEEP>
<PREKEEP>.Op Fl a Ar b<UNKEEP>

...etc.

The `Bk' handler would then be responsible for simply setting the flag 
that would be OR'd in print_mdoc_node() for keeps (SYNPRETTY|KEEPPRETTY 
or whatever).

This way, we can simply say that SYNOPSIS implies a `Bk -words' for the 
entire section (i.e., SYNPRETTY) and that `Bk -words' means that 
contained macro lines aren't space-broken between words.

Thoughts?

Kristaps
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv