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: buffer broken?
Date: Wed, 11 Jan 2012 19:14:03 +0100	[thread overview]
Message-ID: <EF1888D2-A21F-4E32-B79B-87313F14B036@googlemail.com> (raw)
In-Reply-To: <33FF8D55-FCE1-4EA9-B1B6-3D29550424F0@uva.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1609 bytes --]


Am 11.01.2012 um 12:52 schrieb Meer, H. van der:

> 
> 
> On 11 jan. 2012, at 11:33, luigi scarso wrote:
> 
>> 
>> 
>> On Wed, Jan 11, 2012 at 11:11 AM, Hans van der Meer <havdmeer@xs4all.nl> wrote:
>> Something must have been changed with buffers between the versions:
>> ConTeXt  ver: 2011.11.29 18:47 MKIV  fmt: 2011.12.31
>> and
>> ConTeXt  ver: 2012.01.09 10:08 MKIV  fmt: 2012.1.11
>> 
>> Formerly this was ok:
>> \startbuffer[abc]
>> whatever
>> \stopbuffer
>> 
>> Now I get: ! Missing } inserted.
>> 
>> Because running this in isolation goes without a problem, I suspect the change has to do with the project structure in which I use the buffer. But again, it worked in the past.
>> Does it works with 
>> \setbuffer[abc]
>> whatever
>> \endbuffer
>> ?
>> 
> 
> It works with these macros, yes. Thanks.
> 
> But is \setbuffer..\endbuffer something new?

No, it’s a old command but not very useful for a user.

> I do not see it on the Reference page of the wiki.

The original source for the reference pages didn’t provide a way to describe the syntax for \setbuffer but there are also many commands which are undocumented.

> Also it doesn't seem in line with ConTeXt's regular naming scheme of \startsomething..\stopsomething.
> Can you give somewhat more information, for examle what is the difference between \setbuffer and \startbuffer?

\setbuffer can’t be nested like \startbuffer and not a command which should be used in a document. It’s useful for internal use when one write macros where the regular buffer environment can’t be used.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 7144 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
___________________________________________________________________________________

  parent reply	other threads:[~2012-01-11 18:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 10:11 Hans van der Meer
2012-01-11 10:33 ` luigi scarso
2012-01-11 11:52   ` Meer, H. van der
2012-01-11 12:13     ` luigi scarso
2012-01-11 18:14     ` Wolfgang Schuster [this message]
2012-01-11 12:10 ` Hans Hagen
2012-01-11 12:14   ` luigi scarso

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=EF1888D2-A21F-4E32-B79B-87313F14B036@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).