ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Testing the param value
Date: Sun, 6 Jul 2014 22:58:13 +0200	[thread overview]
Message-ID: <4486.54947472296$1404680329@news.gmane.org> (raw)
In-Reply-To: <6FA27DE9-4FEC-4E85-9ABA-1914F06BBD19@gmail.com>

On 2014-07-05 Wolfgang Schuster wrote:
> Am 05.07.2014 um 16:47 schrieb Jan Tosovsky:
> 
> > I am hacking the context index entry rendering... ;-)
> > ... but I am stuck with a simple comparison
> >
> > How can I test the given entry if it equals to the specified one?
> >
> > The following code has no effect.
> >
> > \unexpanded\def\defaultregisterentry#1#2#3#4%
> > % #1:processor #2:internal #3:seeindex #4:word
> >  {\def\currentregisterpageindex{#2}%
> >   % start hacking
> >   \def\myword{#4}%
> >   \ifx\myword{My Primary}
> >      \column % do something
> >   \fi
> >   % stop hacking
> >   \strc_register_injector_process
> >   ...
> >
> > What is the proper syntax?
> 
> 
> This should be possible without hacks but without a example I can't
> provide more than a simple example code.
> 
> \newconditional\IndexState
> 
> \define[1]\IndexInternalCommand
> 
> {\doifelse{#1}{MyPrimary}{\global\settrue\IndexState}{\global\setfalse\
> IndexState}#1}
> 
> \define[1]\IndexCommand
>   {\setfalse\IndexState
>    \setbox\scratchbox\hbox{#1}%
>    \ifconditional\IndexState
>      \column
>    \fi
>    \box\nextbox}
> 
> \setupregister
>   [index]
>   [    textcommand=\IndexCommand,
>    deeptextcommand=\IndexInternalCommand]
> 

Thanks, it looks promising even I am quite lost in this logic :-)

Do I understand correctly that the IndexState is a global boolean which is
set either to true or false when deeptextcommand is processed and when
textcommand is called, it works with this pre-filled variable?

{\setfalse\IndexState % why this? A default value?
 \setbox\scratchbox\hbox{#1}%
 \box\nextbox} % what do these two do?

I am asking as #1 is consumed somehow and there is just a page reference in
the result index. But that break (\column) works correctly.

I've encountered mising words when comparing hashed params directly. Like if
they are read once, they are not available any more. This was the reason why
I used a helper 'myword' variable in my hack.

But I've just written that code analogically to some other conditions found
in the sources without proper knowledge what exactly it does.

Regards, Jan


___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2014-07-06 20:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53b8103b.e25cb40a.6b65.fffffdcaSMTPIN_ADDED_BROKEN@mx.google.com>
2014-07-05 16:56 ` Wolfgang Schuster
2014-07-06 20:58   ` Jan Tosovsky [this message]
2014-07-05 14:47 Jan Tosovsky

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='4486.54947472296$1404680329@news.gmane.org' \
    --to=j.tosovsky@email.cz \
    --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).