From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startmode and \startcomment inside of \def
Date: Sun, 7 Nov 2010 15:53:43 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1011071551110.12558@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <397B899C-EA85-4622-8BAE-B3D35C2508A4@gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 734 bytes --]
On Sun, 7 Nov 2010, Wolfgang Schuster wrote:
>
> Am 07.11.2010 um 20:49 schrieb Vedran Miletić:
>
>> How would I then do something like this?
>>
>> \def\startSolution{\startmode[solutions]\startframedtext}
>> \def\stopSolution{\stopframedtext\stopmode}
>
> \startmode[solution]
> \setupbuffer[Solution][local=no,before=\startframedtext,after=\stopframedtext]
> \stopmode
In general, I agree with Wolfgang. It is better to redefine the macro at
an outer level. You can even do:
\defineframedtext[Solution]
\startnotmode[solution]
\definebuffer[Solution][local=yes]
\stopnotmode
However, in the few cases that you actually need to check for a mode
inside a macro, you can use \doifmode ... etc.
Aditya
[-- Attachment #2: Type: text/plain, Size: 486 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:[~2010-11-07 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 18:42 Vedran Miletić
2010-11-07 19:06 ` Wolfgang Schuster
2010-11-07 19:49 ` Vedran Miletić
2010-11-07 20:20 ` Wolfgang Schuster
2010-11-07 20:53 ` Aditya Mahajan [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=alpine.LNX.2.01.1011071551110.12558@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).