From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml version 1.10.6 available
Date: Tue, 28 Sep 2010 00:44:44 +0200 [thread overview]
Message-ID: <4CA11E5C.4090005@bsd.lv> (raw)
In-Reply-To: <20100927222600.GA5616@iris.usta.de>
> ... and you snoke in a few nice last-minute bug fixes,
> shortening the TODO list. :-)
Ja, I forgot that I hadn't released since the calling convention change
and wanted to push those out before people get too comfortable with the
-W conventions.
These TODOs were really the low-hanging fruit, however. The block stuff
and the dreaded Bl-tab issues remain.
I want to focus on some structural changes in 1.10.7, such as throwing
out {mdoc,man}_action in favour of validate. This will probably bring
with it a chunk of code reductions and clean-ups. I'll probably end up
fixing A. Kozlov's TODO item while I'm at it.
I'm also going to push around some header code as talked about quite
some time ago.
Ingo & Joerg, do the downstream mdoclint scripts have any warnings that
mandoc doesn't? Beyond the `Pp' stuff I just added to the TODO (more
low-hanging fruit).
> This is now merged to OpenBSD as well.
> While merging, i fixed a minor regression:
> Two successive blank lines must both be printed,
> even (horrors!) ouside literal mode.
> Both old and new groff agree on that.
>
> I fixed that by interpreting blank lines as .sp (instead of .Pp)
> in mdoc.c, function mdoc_ptext(), and dropping .Pp before .sp
> in exactly the same way as .Pp before .Pp.
I'm fine with all of these patches (and embarrassed I didn't catch them
myself---especially the Pp insertion in mdoc.c, ouch!).
Thanks again and good work!
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-09-27 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CA0912F.5040103@bsd.lv>
2010-09-27 22:26 ` Ingo Schwarze
2010-09-27 22:44 ` Kristaps Dzonsons [this message]
2010-09-27 23:29 ` 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=4CA11E5C.4090005@bsd.lv \
--to=kristaps@bsd.lv \
--cc=tech@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).