discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: discuss@mdocml.bsd.lv
Subject: desired .Bk semantics?
Date: Sat, 3 Jul 2010 01:43:20 +0200	[thread overview]
Message-ID: <20100702234320.GC6026@iris.usta.de> (raw)

Hi,

after much headbanging while trying to understand tmac files,
i guess i finally figured out what .Bk -words is supposed to do.
It seems it has nothing to do with macros, but simply with -
lines in the input file!  My impression is that .Bk -words
avoids line breaks inside the output generated from each input
line.  Perhaps that's why it is called -words (as opposed to -line).
Duh.

Before i start implementing that - it will be a bit tricky,
because Bk will be the first macro having explicit BLOCKs and
implicit BODYs - i should like to get feedback whether you

 1) agree with my analysis
 2) agree that is sane semantics

As far as i can see, it does seem at least semi-sane and would
probably fix the remaining .Bk issues in our tree.

But i don't want to implement it and then have everybody yell at
me what a bad idea it is.  =:c)

Yours,
  Ingo


P.S.
Running the following test file through groff 1.20.1 (NEW groff)
seems to support my analysis.  Running it through our old groff
just shows how buggy our old groff is.  Oh well...


.Dd July 2, 2010
.Dt BK-BREAK 1
.Os
.Sh NAME
.Nm Bk-break
.Nd handling of word keeps
.Sh SYNOPSIS
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo
.Oo a Oc
.Oo b Oc
.Oc
.Ek
.Pp
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo
.Oo a Oc Oo b Oc
.Oc
.Ek
.Pp
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo a b
.Oc
.Ek
.Pp
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo a
b
.Oc
.Ek
.Pp
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo a Oc b
.Ek
.Pp
.Nm
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x x x
.Ar x x x x x x
.Bk -words
.Oo a Oc
b
.Ek
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2010-07-02 23:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-02 23:43 Ingo Schwarze [this message]
2010-07-03  6:54 ` Jason McIntyre
2010-07-03 12:27   ` Kristaps Dzonsons
2010-07-03 14:11     ` Jason McIntyre
2010-07-03 16:24       ` Kristaps Dzonsons
2010-07-03 16:52         ` Jason McIntyre
2010-07-03 17:25           ` desired .Bk semantics? [UPDATED PATCH] Kristaps Dzonsons
2010-07-03 17:28         ` desired .Bk semantics? 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=20100702234320.GC6026@iris.usta.de \
    --to=schwarze@usta.de \
    --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).