ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Indexes
Date: Tue, 21 May 2002 21:35:37 +0200	[thread overview]
Message-ID: <20020521213537.A975@scaprea> (raw)

Hi,

I have a few questions regarding indexes.

1. \completeindex generates a numbered chapter. Is there a way to make
   this unnumbered?

2. Is there a way to suppress the index when there are no index terms,
   in other words, can I let Context detect whether there are index
   terms? I tried \doifmode{*index}{\completeindex}, but that does not
   seem to do what I want.

3. In the recent beta, which I downloaded on 11 May, \completeindex
   generates an erroneous ToC entry, viz. titleindex. I traced this
   back to an \xdef that does not do what it probably was meant to do:

\convertmeaning #1\to ->\bgroup \honorunexpanded \dontexpandencoding \xdef \@@g
lobalexpanded {#1}\xdef \@@globalexpanded {\@@globalexpanded }\egroup \convertc
ommand \@@globalexpanded \to 
#1<-\headtext {\v!index }

\headtext ->\let \handletextprefix \firstoftwoarguments \dogetupsometextprefix 
\headlanguage \c!titel 

\firstoftwoarguments #1#2->#1
#1<-\dogetupsometextprefix 
#2<-\headlanguage 

\c!titel ->\c!internal! titel
{\string}

\v!index ->index
{\xdef}

\@@globalexpanded ->\let \handletextprefix \dogetupsometextprefix titel{index}

The \let does not work well in \xdef; instead, \firstoftwoarguments is
expanded. I cannot think of a way to correct this.

Regards,
Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl


             reply	other threads:[~2002-05-21 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 19:35 Simon Pepping [this message]
2002-05-21 21:21 ` Indexes Hans Hagen

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=20020521213537.A975@scaprea \
    --to=spepping@scaprea.hobby.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).