From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Churn-ish check-in getting mdoc_parseln() and man_parseln() to
Date: Sun, 27 Jun 2010 18:15:52 +0200 [thread overview]
Message-ID: <4C277938.30005@bsd.lv> (raw)
In-Reply-To: <4C2775AB.5050909@bsd.lv>
>> This must not be const.
>
> Registers should be written only by libroff (they're roff constructs).
> It's up to libmdoc and libman if they want to cue the front-ends by
> looking at both their internal state and the registers. This will be
> apparent by the next commit that implements the cue for SYNOPSIS formatting.
No--on further analysis, I'm wrong:
.Sh FOOBAR
.nr nS 1
.Ft "void"
.Fn config_init "void"
.Sh FOOBAR2
.Ft "void"
.Fn config_init "void"
The `Sh' will reset the register. This, thanks to my last checkin, is a
simple fix. Coming in a few minutes...
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2010-06-27 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201006261536.o5QFacau021968@krisdoz.my.domain>
2010-06-26 20:09 ` Ingo Schwarze
2010-06-27 16:00 ` Kristaps Dzonsons
2010-06-27 16:07 ` Ingo Schwarze
2010-06-27 16:27 ` Kristaps Dzonsons
2010-06-27 16:15 ` Kristaps Dzonsons [this message]
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=4C277938.30005@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).