From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Highlight current chapter in list
Date: Fri, 09 Nov 2012 18:03:44 +0100 [thread overview]
Message-ID: <509D3770.20807@wxs.nl> (raw)
In-Reply-To: <CAF=dkzxTw-qLUHgMus4sYXo2=L31m92MT0CWOs8=5NN3oSuYsg@mail.gmail.com>
On 11/9/2012 5:53 PM, Sietse Brouwer wrote:
> Hans wrote:
>> the next beta has: \namedstructureheadlocation{name}
>> so that you can compare
>> \currentlistentrylocation
>> with
>> \namedstructureheadlocation{chapter}
>> (todo: also store locations elsewhere?)
>> Best document this before we forget about it.
>
> Is this a good description of the command's behavior?
>
> All structure heads, regardless of level, get a location number in the
> order in which they appear. Like so (see also MWE at bottom of this
> e-mail):
>
> \section{Alpha}
> % location number: 1; type: section; section number: 1
> \section{Beta}
> % location number: 2; type: section; section number: 2
> \subsection{Aap}
> % location number: 3; type: subsection; subsection number: 1
> \subsection{Noot}
> % location number: 4; type: subsection; subsection number: 2
> \section{Gamma}
> % location number: 5; type: section; section number: 3
>
> \namedstructureheadlocation{X} then returns the location number of the
> current X, where X is the name of a structure level (e.g. 'chapter',
> 'section', etc.)
>
> If you ask for e.g. \namedstructureheadlocation{chapter}, and you are
> not in a chapter, then 0 is returned.
>
> Anything missing?
a location number is some kind of unique internal reference, a pretty
old feature btw, dating from the early days of context, when complex
interactivity was added, but it comes in handy here
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-09 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 23:29 Marco Patzer
2012-11-08 8:44 ` Wolfgang Schuster
2012-11-08 10:06 ` Marco Patzer
2012-11-08 11:06 ` Hans Hagen
2012-11-08 11:15 ` Hans Hagen
2012-11-08 11:42 ` Marco Patzer
2012-11-08 17:32 ` Marco Patzer
2012-11-08 18:18 ` Hans Hagen
2012-11-09 16:53 ` Sietse Brouwer
2012-11-09 17:03 ` Hans Hagen [this message]
2012-11-08 21:37 ` Marco Patzer
2012-11-08 21:45 ` Marco Patzer
2012-11-08 21:48 ` Wolfgang Schuster
2012-11-08 22:16 ` Hans Hagen
2012-11-09 0:43 ` Tikz backgrounds (was Re: Highlight current chapter in list) Aditya Mahajan
2012-11-09 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=509D3770.20807@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).