ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: A problem with modes
Date: Wed, 27 Jun 2012 05:23:42 +0200	[thread overview]
Message-ID: <3ADDC0E7-1F5B-446C-A6E9-9F985112D536@googlemail.com> (raw)
In-Reply-To: <20120626232537.00553f9b@aga-netbook>


Am 26.06.2012 um 23:25 schrieb Marcin Borkowski:

>>> Or is there a better way to do something like this?
>> 
>> It depends on what you want to do. You can create a buffer command:
>> 
>> \def\startamode{\grabbufferdata[amode][startamode][stopamode]}
>> %\def\stopamode {\getbuffer[amode]}
>> 
>> \starttext
>> 
>> All modes.
>> \startamode
>> “A” mode.
>> \stopamode
>> 
>> \stoptext
> 
> Thanks, it worked.  One question: is there any difference between
> 
> \def\starta{...}
> \def\stopa{...}
> 
> and
> 
> \definestartstop[a][before={...},after={…}]

Yes because in my definition for \startamode I start a buffer which reads everything
untill the delimiting \stopamode and stores it in memory, afterwards you can access
the stored content with \getbuffer[…]. When you use \definestartstop to create
the environment you have only two commands which perform a few things at the begin
and end of the environment but you can do much with the content itself, the only
way to gobble the content is to store it in a box but than the buffer method is easier.

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
___________________________________________________________________________________


      reply	other threads:[~2012-06-27  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 20:12 Marcin Borkowski
2012-06-26 20:40 ` Aditya Mahajan
2012-06-26 20:44 ` Wolfgang Schuster
2012-06-26 21:25   ` Marcin Borkowski
2012-06-27  3:23     ` 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=3ADDC0E7-1F5B-446C-A6E9-9F985112D536@googlemail.com \
    --to=schuster.wolfgang@googlemail.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).