From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \index inserts whitespace
Date: Fri, 10 Jul 2009 20:03:22 +0200 [thread overview]
Message-ID: <4A57826A.3060600@wxs.nl> (raw)
In-Reply-To: <E120921D-7FE4-4BFE-AF12-12C5D996F8A1@gmail.com>
Wolfgang Schuster wrote:
>
> Am 09.07.2009 um 23:16 schrieb Hans Hagen:
>
>> \def\donoregister
>> #1#2#3{\doflushatpar{\doprocesspageregister{#1}{}{}{#2}{#3}}} %
>> register key - entry
>> \def\dodoregister#1#2#3#4{\doflushatpar{\doprocesspageregister{#1}{}{#2}{#3}{#4}}}
>> % register key altnum entry
>
> Thanks, this works.
>
> Is there also a way to take care of situations where the \index command
> appear between two vertical skips, a stupid example is
no, an index inserts something in the stream (after all it has to be
anchored); in such a case you can try \EveryPar{\index{...}} (or use the
delayed flush at par mechanism)
> \starttext
>
> text
> \blank\index{text}
>
> \blank
> more text
>
> \stoptext
>
> In my document this appears in the form
>
> \setup[commanda]\index{commanda}
>
> \setup[commandb]\index{commandb}
>
> and
>
> \setup[commandc]\index{commandc}
>
> \starttyping
> ...
> \stoptyping
>
> Wolfgang
>
>
> ___________________________________________________________________________________
>
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-10 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 19:48 Wolfgang Schuster
2009-07-09 21:16 ` Hans Hagen
2009-07-10 17:27 ` Wolfgang Schuster
2009-07-10 18:03 ` Hans Hagen [this message]
2009-07-11 3:44 ` Wolfgang Schuster
2009-07-11 9:17 ` 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=4A57826A.3060600@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).