From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reference to structureuservariable
Date: Mon, 20 Jan 2014 10:47:24 +0100 [thread overview]
Message-ID: <ced178e0-6d74-4f95-a445-217a1add06d0@keima.localdomain> (raw)
In-Reply-To: <87ha8zvvpm.fsf@micropit.couberia.selfip.net>
[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]
Hi Peter,
you can use \namedstructureuservariable{section}{foo} to access the foo variable of the section.
Wolfgang
On 20.01.2014 10:39:01, Peter Münster <pmlists@free.fr> wrote: Hi,
How can I read a structureuservariable at the end of the section, when
there are subsections? Example:
--8<---------------cut here---------------start------------->8---
\starttext
\startsection[title=sec][foo=bar]
% \edef\myFoo{\structureuservariable{foo}} % workaround
\startsubsection[title=sub 1]
sub 1
\stopsubsection
\startsubsection[title=sub 2]
sub 2
\stopsubsection
\par
foo is \structureuservariable{foo}.
% foo is \myFoo. % workaround
\stopsection
\startsection[title=sec][foo=bar]
no subsections...\par
foo is \structureuservariable{foo}.
\stopsection
\stoptext
--8<---------------cut here---------------end--------------->8---
Is there a clean way or do I need to use something like the above
workaround?
TIA for any hints,
--
Peter
___________________________________________________________________________________
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
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 1815 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2014-01-20 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 9:39 Peter Münster
2014-01-20 9:47 ` Wolfgang Schuster [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=ced178e0-6d74-4f95-a445-217a1add06d0@keima.localdomain \
--to=schuster.wolfgang@gmail.com \
--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).