From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Ingo Schwarze <schwarze@usta.de>,
"tech@mdocml.bsd.lv" <tech@mdocml.bsd.lv>
Subject: Re: [PATCH] .nr for mdoc(7)]
Date: Sat, 26 Jun 2010 17:32:31 +0200 [thread overview]
Message-ID: <4C261D8F.30102@bsd.lv> (raw)
In-Reply-To: <20100626122711.GA15113@iris.usta.de>
Ingo et al.,
I've begun implementing a bit of a re-write of this patch. You can see
it in the commit I just checked in. Here's how I'm laying it out.
Basically, I'm adding generic support for registers. They're set in
libroff and propogate into libmdoc and libman, which will do whatever
(e.g., cue front-ends).
Steps:
(1) Add regs.h, which defines possible registers and their values.
This is done.
(2) roff_parseln() gets a non-const struct regset and can modify the
values. See roff.c for this parsing. This is done.
(3) libmdoc and libman receive a const regset. They operate on these
values in their own ways to cue the front-end or change their parse
behaviour. This is not yet done.
(4) The front-ends response to cues. Not yet done.
Thoughts?
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next parent reply other threads:[~2010-06-26 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100626122711.GA15113@iris.usta.de>
2010-06-26 15:32 ` Kristaps Dzonsons [this message]
2010-06-16 2:11 [PATCH] .nr for mdoc(7) 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=4C261D8F.30102@bsd.lv \
--to=kristaps@bsd.lv \
--cc=schwarze@usta.de \
--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).