ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: NTG ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re: \index eats \par?
Date: Fri, 26 Oct 2001 12:18:43 +0200	[thread overview]
Message-ID: <5.1.0.14.1.20011026121618.032a18d0@server-1> (raw)
In-Reply-To: <20011025190854.A17304@bart.math.muni.cz>

At 07:08 PM 10/25/2001 +0200, David Antos wrote:

>         Hi all,
>
>using \index at the end of a paragraph (like this one ;-) eats all \par-s
>after that. Is this a bug or a feature? (In human words: the paragraphs become
>joined together into one.)
>\index{really don't know why}
>
>It can be easilly overriden using \index{} before the end of the paragraph,
>but I consider this quite unpleasant.

actually this is a feature; as berend says: use \index before the word to 
index (think of this: if such a word hyphenates, you want the ref on the 
page where the forst part ends up).

the idea is as follows:

\chapter {something}
\index{oeps}
\index{more}

some text

now this works well, if the \par would not be eaten, there would be a write 
node and thereby interference in the spacing (in some situations resulting 
in too much whitespace for instance.

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


      parent reply	other threads:[~2001-10-26 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 17:08 David Antos
2001-10-25 18:30 ` Berend de Boer
2001-10-26 10:18 ` Hans Hagen [this message]

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=5.1.0.14.1.20011026121618.032a18d0@server-1 \
    --to=pragma@wxs.nl \
    --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).