From: Pavel Stupin <grosso@mail.ru>
Subject: Re: \index + \definedescription
Date: Fri, 10 Oct 2003 15:15:34 +0800 [thread overview]
Message-ID: <20031010151534.274f5827.grosso@mail.ru> (raw)
In-Reply-To: <6.0.0.22.1.20031009092931.01b4e688@digitpaint.nl>
____________________________________________________
On Thu, 09 Oct 2003 09:47:51 +0200
Willi Egger <w.egger@boede.nl> wrote:
____________________________________________________
> Possibly the following approach can help:
>
> Define a list \definelist[name][options]
> Write to this list at each entry of the description \writetolist[name]{text}
> At the spot where the list should occur \placelist[name]
>
> Programmers might write a macro which could be used in the description
> definition together with e.g. [after=\TheMacro] which writes into the list.
Thank you, Willi!
Your solution works, but I've figured out a very simple, though probably not very elegant one:
defined \def\dictind#1{\startDictEntry{#1}\index{#1}} and replaced all \startDictEntry w/ \dictind.
Best, Pavel.
next prev parent reply other threads:[~2003-10-10 7:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 4:27 Pavel Stupin
2003-10-09 7:47 ` Willi Egger
2003-10-10 7:15 ` Pavel Stupin [this message]
2003-10-10 18:19 ` Willi Egger
2003-10-12 3:48 ` itemize: before/after only with columns? Gary Pajer
2003-10-28 13:29 ` another itemize question Gary Pajer
2003-10-29 8:49 ` Willi Egger
2003-10-29 22:57 ` Patrick Gundlach
2003-10-30 2:41 ` Gary Pajer
2003-10-30 15:48 ` Patrick Gundlach
2003-10-31 3:44 ` Gary Pajer
2003-10-31 8:34 ` Patrick Gundlach
2003-10-30 2:48 ` Gary Pajer
2003-10-30 2:54 ` Gary Pajer
2004-04-16 18:50 ` Baffling error Paulo Ney de Souza
2004-04-16 19:24 ` Willi Egger
2004-04-16 19:29 ` Paulo Ney de Souza
2004-04-16 19:51 ` Willi Egger
2004-04-16 19:56 ` Paulo Ney de Souza
2004-04-16 20:10 ` Willi Egger
2004-04-16 20:18 ` Paulo Ney de Souza
2004-04-16 20:36 ` Willi Egger
2004-04-17 11:44 ` George N. White III
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=20031010151534.274f5827.grosso@mail.ru \
--to=grosso@mail.ru \
--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).