From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Something changed with \index command
Date: Sun, 08 Oct 2000 00:07:57 +0200 [thread overview]
Message-ID: <3.0.6.32.20001008000757.008cf6a0@pop.wxs.nl> (raw)
In-Reply-To: <39DE2600.3FE45A0F@pobox.com>
At 09:20 PM 10/6/00 +0200, Berend de Boer wrote:
>Hello All,
>
>For some time I've noticed that the behaviour of the \index command
>seems to have changed (perhaps I'm mistaken).
I checked an old archive and nothing seems to be changed. This is rather
old code btw.
>Things as:
>
> my hello\index{hello} world program.
>
>do not work as the space after \index is eaten. I now need to write:
>
> my hello\index{hello}{} world program.
>
>Is this a bug or am I simply mistaken that previous behaviour was
>different?
The \index command has always eaten up spaces and pars. This means that in
\section{Did you know that Berend}
\index{de Boer}
is a clever programmer.
the \index write node will not interfere and the index indeed is attached
to the right location.
Also think of:
bla \index{well} theindexbelongstothisword
where the long work ends up on the next page. So:
abc \index{def} ghi == abc \index{def}ghi
with the following alternative:
\def\complexdoregister[#1]#2% just an example, this code will not be used
{\doprocesspageregister[#1]{#2}%
\ifvmode\nobreak\expandafter\GotoPar\fi}
the space is obeyed but I prefer the method where the index *precedes* the
word since it's more secure.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
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
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-10-07 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-06 19:20 Berend de Boer
2000-10-07 22:07 ` Hans Hagen [this message]
2000-10-09 18:45 ` Berend de Boer
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=3.0.6.32.20001008000757.008cf6a0@pop.wxs.nl \
--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).