Re: Giving up on emulating SYNOPSIS vspace.

[Ingo Schwarze <schwarze@usta.de>]

Hi Kristaps,

> First, I propose that SYNOPSIS sections be grouped into the
> following macro sets,
> 
>  .In
>  .Ft/Fn ("combo", i.e., one after the other)
>  .Ft/Fo (same)
>  .Fo
>  .Fn
>  .Fd
> 
> with rules as follows.  Any macro/combo of these sets will be
> preceded and proceeded by a newline.  It doesn't matter what the
> hell comes before or after or whether these are line macros or not.
> 
> Next, non-like pair-wise sets will be separated by a single vertical space.
> 
> Lastly, like pairwise Ft/Fn, Ft/Fo, Fo, and Fn are separated by a
> single vertical space.

That definitely sounds sane, and it covers the most important use cases.

I'm not 100% sure this covers all sane use cases, even though i couldn't
name a real-world manual page that needs additional rules, off the top
of my head.

So, i think implementing this has good chances to be OK;
there is a small risk it turns out to not be better in practice
than what we have now, but in that case it will hopefully not be
too difficult to add the missing feature(s).

[...]
> move on with PostScript and Ingo's block-breaking patches.

Oh, you don't have the final version yet, what you have is
 1) known buggy
 2) not feature-complete

I need to check that the final version in my tree is really
complete and correct, extract it and post it.  I hope to get
round to that.  It's really the next thing i should do with
respect to mandoc, now that 1.10.1 is merged into OpenBSD.

Yours,
  Ingo
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv