From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Place an annotation before it is defined
Date: Mon, 7 Jan 2013 22:57:55 +0100 [thread overview]
Message-ID: <34165F64-B92B-44E0-A44B-92EED708201F@gmail.com> (raw)
In-Reply-To: <20130107214957.GX11551@homerow>
Am 07.01.2013 um 22:49 schrieb Marco Patzer <homerow@lavabit.com>:
> On 2013–01–07 Hans Hagen wrote:
>
>> buffers (or blocks)
>
> Buffers apparently can't be used before the content is defined, but
> it works for blocks (I never used them). Test:
>
> \defineblock [bar]
>
> \starttext
>
> buf: \getbuffer[foo]
> BBBBBBBBBBB
>
> \startbuffer[foo]
> buf: AAAAAAAAAAA
> \stopbuffer
>
> \useblocks [bar]
> DDDDDDDDDDD
>
> \beginbar
> block: CCCCCCCCCCC
> \endbar
>
> \stoptext
>
> Is there a reason why the blocks favour begin/end instead of
> start/stop? Looks weird somehow.
Blocks use begin/end to allow the same name for the environment as other commands, e.g. for exams:
\defineblock[question]
\defineblock[answer]
\hideblocks[answer]
\defineenumeration[question]
\defineenumeration[answer]
\starttext
\chapter{Questions} % Show only the question blocks
\beginquestion
\startquestion
First question.
\stopquestion
\endquestion
\beginanswer
\startasnwer
Answer to the first question.
\stopanswer
\endanswer
\chapter{Answers} % Show the question with the corresponding answer
\useblocks[question,answer]
\stoptext
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-01-07 21:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 21:20 Marco Patzer
2013-01-07 21:25 ` Hans Hagen
2013-01-07 21:49 ` Marco Patzer
2013-01-07 21:57 ` Wolfgang Schuster [this message]
2013-01-07 22:20 ` Jaroslav Hajtmar
2013-01-07 22:25 ` Wolfgang Schuster
2013-01-07 22:28 ` Marco Patzer
2013-01-07 21:59 ` Hans Hagen
2013-01-07 21:34 ` Wolfgang Schuster
2013-01-07 21:56 ` Marco Patzer
2013-01-07 22:01 ` Wolfgang Schuster
2013-01-07 22:20 ` Marco Patzer
2013-01-10 21:21 ` Wolfgang Schuster
2013-01-11 8:45 ` Marco Patzer
2013-01-11 16:08 ` Wolfgang Schuster
2013-01-11 17:06 ` Marco Patzer
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=34165F64-B92B-44E0-A44B-92EED708201F@gmail.com \
--to=wolfgang.schuster@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).