From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \index{…} causes space
Date: Fri, 24 Dec 2010 12:57:26 +0100 [thread overview]
Message-ID: <E2B0D092-2B77-423E-A7BC-6EF9FC9B3D00@uni-koblenz.de> (raw)
In-Reply-To: <201012241253.47153.alan.braslau@cea.fr>
[-- Attachment #1.1: Type: text/plain, Size: 763 bytes --]
Am 24.12.2010 um 12:53 schrieb Alan BRASLAU:
> On Friday 24 December 2010 11:54:17 Taco Hoekwater wrote:
>>> On 12/24/2010 11:48 AM, Andreas Harder wrote:
>>> \index{test}test
>>
>> \ignorespaces could be possibly be added to \index in your case,
>> but that does not solve this conceptual problem: what is actually
>> being indexed in that second line? Not the word on the left
>> (as that could be on a different page), neither the word on the
>> right (as that could also be on a different page).
>
> I have understood that the correct use of \index{}
> is immediately following the word to be indexed, as in:
> test\index{test}
The wiki (http://wiki.contextgarden.net/Registers#Example) suggests it the other way round …?
Andreas
[-- Attachment #1.2: Type: text/html, Size: 1522 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-24 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 10:48 Andreas Harder
2010-12-24 10:54 ` Taco Hoekwater
2010-12-24 11:53 ` Alan BRASLAU
2010-12-24 11:57 ` Andreas Harder [this message]
2010-12-25 10:18 ` Alan BRASLAU
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=E2B0D092-2B77-423E-A7BC-6EF9FC9B3D00@uni-koblenz.de \
--to=aharder@uni-koblenz.de \
--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).