From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-2.sys.kth.se (smtp-2.sys.kth.se [130.237.32.160]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id o65Abo5w029018 for ; Mon, 5 Jul 2010 06:37:51 -0400 (EDT) Received: from smtp-2.sys.kth.se (localhost [127.0.0.1]) by smtp-2.sys.kth.se (Postfix) with ESMTP id 7572014D7CC for ; Mon, 5 Jul 2010 12:37:45 +0200 (CEST) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-2.sys.kth.se ([127.0.0.1]) by smtp-2.sys.kth.se (smtp-2.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1zZloGAsdRFu for ; Mon, 5 Jul 2010 12:37:44 +0200 (CEST) X-KTH-Auth: kristaps [130.237.221.96] X-KTH-mail-from: kristaps@bsd.lv X-KTH-rcpt-to: tech@mdocml.bsd.lv Received: from [130.237.221.96] (ctime.pdc.kth.se [130.237.221.96]) by smtp-2.sys.kth.se (Postfix) with ESMTP id 10A9314C12F for ; Mon, 5 Jul 2010 12:37:42 +0200 (CEST) Message-ID: <4C31B55E.3030202@bsd.lv> Date: Mon, 05 Jul 2010 12:35:10 +0200 From: Kristaps Dzonsons User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090707) X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 To: tech@mdocml.bsd.lv Subject: Re: Bk -words badness References: <4C31A369.6010005@bsd.lv> In-Reply-To: <4C31A369.6010005@bsd.lv> Content-Type: multipart/mixed; boundary="------------020804040402060408030103" This is a multi-part message in MIME format. --------------020804040402060408030103 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit > 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 > ... The enclosed patch is a first stab at this. It only works for explicit `Bk -words' for now; it's trivial to extend this to SYNPRETTY. As you can see, it simply checks whether it's in a KEEP mode and resets to PREKEEP if it's a line subsequent the prior node. This fixes the badness mentioned above. Thoughts? Kristaps --------------020804040402060408030103 Content-Type: text/plain; name="patch.txt" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="patch.txt" PyAuZm9vLjEuc3dwCj8gY29uZmlnLmgKPyBjb25maWcubG9nCj8gZm9vLjEKPyBmb28uMS5o dG1sCj8gZm9vLjMKPyBmb28uNwo/IGZvby5odG1sCj8gbWFuZG9jCj8gcGF0Y2gudHh0Cj8g cmVsYXlkLjgKPyByZWxheWQuOC5odG1sCj8gc3BhbWQuOAo/IHNzaC4xCj8gc3NoLjEuaHRt bAo/IHJlZ3Jlc3Mvb3V0cHV0CkluZGV4OiBtZG9jX3Rlcm0uYwo9PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJD UyBmaWxlOiAvdXNyL3Zob3N0cy9tZG9jbWwuYnNkLmx2L2N2cy9tZG9jbWwvbWRvY190ZXJt LmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuMTcxCmRpZmYgLXUgLXIxLjE3MSBtZG9jX3Rl cm0uYwotLS0gbWRvY190ZXJtLmMJNCBKdWwgMjAxMCAyMjowNDowNCAtMDAwMAkxLjE3MQor KysgbWRvY190ZXJtLmMJNSBKdWwgMjAxMCAxMDozNjo1NyAtMDAwMApAQCAtMzMwLDYgKzMz MCwyMyBAQAogCWVsc2UgaWYgKHRlcm1hY3RzW24tPnRva10ucHJlICYmIEVOREJPRFlfTk9U ID09IG4tPmVuZCkKIAkJY2hsZCA9ICgqdGVybWFjdHNbbi0+dG9rXS5wcmUpKHAsICZucGFp ciwgbSwgbik7CiAKKwkvKgorCSAqIEtlZXBzIG9ubHkgd29yayB1bnRpbCB0aGUgZW5kIG9m IGEgbGluZS4gIElmIGEga2VlcCB3YXMKKwkgKiBpbnZva2VkIGluIGEgcHJpb3IgbGluZSwg cmV2ZXJ0IGl0IHRvIFBSRUtFRVAuCisJICovCisKKwlpZiAoVEVSTVBfS0VFUCAmIHAtPmZs YWdzKSB7CisJCWlmIChuLT5wcmV2ICYmIG4tPnByZXYtPmxpbmUgIT0gbi0+bGluZSkgewor CQkJcC0+ZmxhZ3MgJj0gflRFUk1QX0tFRVA7CisJCQlwLT5mbGFncyB8PSBURVJNUF9QUkVL RUVQOworCQl9IGVsc2UgaWYgKE5VTEwgPT0gbi0+cHJldikgeworCQkJaWYgKG4tPnBhcmVu dCAmJiBuLT5wYXJlbnQtPmxpbmUgIT0gbi0+bGluZSkgeworCQkJCXAtPmZsYWdzICY9IH5U RVJNUF9LRUVQOworCQkJCXAtPmZsYWdzIHw9IFRFUk1QX1BSRUtFRVA7CisJCQl9CisJCX0K Kwl9CisKIAlpZiAoY2hsZCAmJiBuLT5jaGlsZCkKIAkJcHJpbnRfbWRvY19ub2RlbGlzdChw LCAmbnBhaXIsIG0sIG4tPmNoaWxkKTsKIAo= --------------020804040402060408030103-- -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv