From: Duncan Hothersall <dh@capdm.com>
Subject: Re: register ranges
Date: Thu, 23 Feb 2006 11:10:31 +0000 [thread overview]
Message-ID: <43FD9827.8090004@capdm.com> (raw)
In-Reply-To: <mailman.7.1140692402.12786.ntg-context@ntg.nl>
> \startregister[index]{Menippean}
> \stopregister[index]
>
> and it works. However, when I try to replace [index] with my own key
> (because I have overlapping ranges)
>
> \startregister[satire]{Menippean}
> \stopregister[satire]
>
> I get errors: ...
Hi Thomas.
The first [...] in the \startregister command is the name of the
register itself, then there is a second one for the sort key/range
identifier. So you want:
\startregister[index][Menippean]{Menippean}
\stopregister[index][Menippean]
and then you can have
\startregister[index][Menippean1]{Menippean}
\stopregister[index][Menippean1]
as well.
Hope that helps.
Duncan
next parent reply other threads:[~2006-02-23 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7.1140692402.12786.ntg-context@ntg.nl>
2006-02-23 11:10 ` Duncan Hothersall [this message]
2006-02-23 11:13 ` Thomas A. Schmitz
2006-02-23 10:04 Thomas A. Schmitz
2006-02-23 11:12 ` Taco Hoekwater
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=43FD9827.8090004@capdm.com \
--to=dh@capdm.com \
--cc=ntg-context@ntg.nl \
/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).