Re: [NTG-context] Perhaps missing braces in buff-ini.mkiv?

2016-09-06 Thread Hans Hagen 

On 9/6/2016 8:45 PM, Henri Menke wrote:

On 09/06/2016 10:36 AM, Hans Hagen wrote:

On 9/6/2016 9:05 AM, Henri Menke wrote:

Bump

On 08/09/2016 10:54 AM, Henri Menke wrote:

Dear list,

it seems as if there are braces missing in the definition of \buff_save around 
#2.

\def\buff_save[#1][#2]%
  {...
{\setupcurrentsavebuffer[\c!list={#1},\c!file=#2]}%
  ...}

I think they are missing, because it makes the following work, even though 
arguments and key-value arguments shouldn't be mixed up.

\startbuffer[hash]
foo
\stopbuffer
\savebuffer[hash][hello.txt,prefix=no]
\starttext
\stoptext

I think you should either make a third argument for a key-value list or just 
make the second argument the key-value list.  Then users could input 
\savebuffer[hash][file=hello.txt,prefix=no].


the first argument can be a key/value list in which case the second one is 
ignored

\savebuffer[list=hash,file=hello.txt,prefix=no]


I'd still recommend adding braces around this #2.  Imagine a user does this

\savebuffer[hash][my,file,name,with,commas.txt]


such behaviour is true for all kind of things, normally a user will then 
add the { }


also, using commas in filenames is not that clever

Hans


-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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
___

Re: [NTG-context] Indentation after margin float with caption

2016-09-06 Thread Aditya Mahajan 

On Tue, 6 Sep 2016, Wolfgang Schuster wrote:


 Mikael P. Sundqvist 
 6. September 2016 um 21:07

 Dear all,

 since I got no answer here I cross posted on stackexchange (see
 http://tex.stackexchange.com/q/328147/52406). Now, I got a solution to
 this from Aditya. It seems that it is not yet clear to me (or Aditya,
 as far as I understand from the reply) which float placements that
 respects the \setupfloats[indentnext=yes] and which not. Or more
 importantly, why.

 To make this email thread more complete, the solution of Aditya adds

 \unprotect
 \def\page_one_place_float_auto
 {\page_one_place_float_otherwise\nonoindentation}
 \def\page_one_place_float_bottom
 {\page_one_place_float_otherwise\nonoindentation}
 \def\page_one_place_float_margin
 {\page_margin_blocks_process_float\nonoindentation}
 \def\page_one_place_float_leftmargin
 
{\page_one_place_float_side_indeed\page_sides_process_float_leftmargin\nonoindentation}
 
\def\page_one_place_float_rightmargin{\page_one_place_float_side_indeed\page_sides_process_float_rightmargin\nonoindentation}
 \protect
When backwards compatiblity is a reason for not changing this adding a hook 
can be solution, e.g.


-\def\page_one_place_float_auto   {\page_one_place_float_otherwise}
+\def\page_one_place_float_auto 
{\page_one_place_float_otherwise\rootfloatparameter\c!next}


which can be used with \setupfloat[next=\indentation]


In the move to MkII to MkIV, there have been many changes that are not 
backward compatible. So, I am not in favor of adding a new key when we 
already have an indentnext key just for the sake of backward 
compatibility.


It will be nice if all the location alternatives in setupfloat honored the 
indentnext key. It is really awkaward that when indentnext=yes (or auto) 
location=top and location=bottom behave differently.


If backward compatibility is really important, we could add a mechanism to 
control the indentnext key for each location; but that would add too much 
complexity to the code for very little benefit. If one wants to mix floats 
that indent the next paragraph with floats that don't indent the next 
paragraph, it is possible to define different types of floats (with the 
same counters and lists) such that indentnext=yes for one type and 
indentnext=no for the other.


Aditya
___
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
___

Re: [NTG-context] Get "right" numbers using blocks and enumerations

2016-09-06 Thread Mikael P. Sundqvist 
On Tue, Sep 6, 2016 at 9:29 PM, Wolfgang Schuster
 wrote:
> Mikael P. Sundqvist
> 1. September 2016 um 21:18
> Hi,
>
> I'm trying to use blocks for answers in a text, but cannot get the
> numbering to work as I want. I have read about \processblocks at the
> wiki (http://wiki.contextgarden.net/Command/processblocks), but I'm
> not sure that is my cure. I probably miss something easy...
>
> The problem is probably easiest shown by an example:
>
> %%%
> \defineblock[A]
> \hideblocks[A]
>
> \defineenumeration[A][
> text=A,
> prefix=yes,
> prefixsegments=chapter,
> way=bychapter,
> ]
>
> \starttext
>
> \chapter{First chapter}
>
> \beginA
> \startA
> My first answer in the first chapter.
> \stopA
> \endA
>
> \beginA
> \startA
> My second answer in the first chapter.
> \stopA
> \endA
>
>
> \chapter{Second chapter}
>
> \beginA
> \startA
> My first answer in the second chapter.
> \stopA
> \endA
>
> \beginA
> \startA
> My second answer in the second chapter.
> \stopA
> \endA
>
> \chapter{Answers}
> \useblocks[A]
> \stoptext
> %%%
>
> I get, in the Answer chapter
>
> A 3.1, A 3.2, A 3.3 and A 3.4.
>
> What I want to have in the answer chapter is
>
> A 1.1, A 1.2, A 2.1 and A 2.2.
>
> (to follow the numbering in the chapters where the blocks were defined).
>
> Is it possible? What have I missed?
>
> Blocks only store their content without expanding counters etc. and when
> you flush them you have the same result as putting them into the appendices
> by hand.
>
> Related: Is there a better way to set answers to questions? (Perhaps
> not having to write both the \begin... \start... \stop... \end... for
> every question?
>
> \setupblock[A][before=\startA,after=\stopA]
>
> but you can’t use the optional argument for a enumerations anymore (e.g. to
> set a title) with this method.
>
> 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
> ___

Many thanks for your reply, Wolfgang (also in the other thread, but I
don't reply there, since I have nothing more to add at the moment). I
then leave the idea of having the blocks processed "where they are
written".

For now, I solve this by adding labels on all exercises, and refer to
them in the answers. It works, but my fantasy for naming the labels
are soon reaching the limit... :)

Best regards, Mikael
___
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
___

Re: [NTG-context] Get "right" numbers using blocks and enumerations

2016-09-06 Thread Wolfgang Schuster 

Mikael P. Sundqvist 
1. September 2016 um 21:18
Hi,

I'm trying to use blocks for answers in a text, but cannot get the
numbering to work as I want. I have read about \processblocks at the
wiki (http://wiki.contextgarden.net/Command/processblocks), but I'm
not sure that is my cure. I probably miss something easy...

The problem is probably easiest shown by an example:

%%%
\defineblock[A]
\hideblocks[A]

\defineenumeration[A][
text=A,
prefix=yes,
prefixsegments=chapter,
way=bychapter,
]

\starttext

\chapter{First chapter}

\beginA
\startA
My first answer in the first chapter.
\stopA
\endA

\beginA
\startA
My second answer in the first chapter.
\stopA
\endA


\chapter{Second chapter}

\beginA
\startA
My first answer in the second chapter.
\stopA
\endA

\beginA
\startA
My second answer in the second chapter.
\stopA
\endA

\chapter{Answers}
\useblocks[A]
\stoptext
%%%

I get, in the Answer chapter

A 3.1, A 3.2, A 3.3 and A 3.4.

What I want to have in the answer chapter is

A 1.1, A 1.2, A 2.1 and A 2.2.

(to follow the numbering in the chapters where the blocks were defined).

Is it possible? What have I missed?

Blocks only store their content without expanding counters etc. and when
you flush them you have the same result as putting them into the appendices
by hand.

Related: Is there a better way to set answers to questions? (Perhaps
not having to write both the \begin... \start... \stop... \end... for
every question?

\setupblock[A][before=\startA,after=\stopA]

but you can’t use the optional argument for a enumerations anymore (e.g. 
to set a title) with this method.


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
___

Re: [NTG-context] Indentation after margin float with caption

2016-09-06 Thread Wolfgang Schuster 

Mikael P. Sundqvist 
6. September 2016 um 21:07

Dear all,

since I got no answer here I cross posted on stackexchange (see
http://tex.stackexchange.com/q/328147/52406). Now, I got a solution to
this from Aditya. It seems that it is not yet clear to me (or Aditya,
as far as I understand from the reply) which float placements that
respects the \setupfloats[indentnext=yes] and which not. Or more
importantly, why.

To make this email thread more complete, the solution of Aditya adds

\unprotect
\def\page_one_place_float_auto
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_bottom
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_margin
{\page_margin_blocks_process_float\nonoindentation}
\def\page_one_place_float_leftmargin
{\page_one_place_float_side_indeed\page_sides_process_float_leftmargin\nonoindentation}
\def\page_one_place_float_rightmargin{\page_one_place_float_side_indeed\page_sides_process_float_rightmargin\nonoindentation}
\protect
When backwards compatiblity is a reason for not changing this adding a 
hook can be solution, e.g.


-\def\page_one_place_float_auto   {\page_one_place_float_otherwise}
+\def\page_one_place_float_auto   
{\page_one_place_float_otherwise\rootfloatparameter\c!next}


which can be used with \setupfloat[next=\indentation]

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
___

Re: [NTG-context] Indentation after margin float with caption

2016-09-06 Thread Mikael P. Sundqvist 
On Fri, Sep 2, 2016 at 9:47 AM, Mikael P. Sundqvist  wrote:
> Dear list,
>
> is it possible to have a margin figure with caption, and automatically
> have the next paragraph indented? Look at the example below (pdf
> result attached). If I add the none argument to the float, then the
> next paragraph is indented. Otherwise not. Is it a bug or a feature?
>
> Best regards, Mikael
>
> \setupindenting[yes,medium]
>
> \setupfloats[indentafter=yes]
>
> \starttext
>
> \input tufte
>
> \placefigure[outermargin,middle]{}{\blackrule[width=1cm,height=1cm]}
>
> This should be indented, but it is not! \input tufte
>
> \input tufte
>
> \placefigure[outermargin,middle,none]{}{\blackrule[width=1cm,height=1cm]}
>
> This should be indented, and it is! But I want the caption. \input tufte
> \stoptext

Dear all,

since I got no answer here I cross posted on stackexchange (see
http://tex.stackexchange.com/q/328147/52406). Now, I got a solution to
this from Aditya. It seems that it is not yet clear to me (or Aditya,
as far as I understand from the reply) which float placements that
respects the \setupfloats[indentnext=yes] and which not. Or more
importantly, why.

To make this email thread more complete, the solution of Aditya adds

\unprotect
\def\page_one_place_float_auto
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_bottom
{\page_one_place_float_otherwise\nonoindentation}
\def\page_one_place_float_margin
{\page_margin_blocks_process_float\nonoindentation}
\def\page_one_place_float_leftmargin
{\page_one_place_float_side_indeed\page_sides_process_float_leftmargin\nonoindentation}
\def\page_one_place_float_rightmargin{\page_one_place_float_side_indeed\page_sides_process_float_rightmargin\nonoindentation}
\protect

(this kind of solution was also suggested in 2011 in an old thread,
see https://mailman.ntg.nl/pipermail/ntg-context/2011/058152.html)

/Mikael

PS I have a couple of more questions on the list that has not got any
response. I hope you don't mind me cross posting on stackexchange in
these cases.
___
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
___

Re: [NTG-context] Perhaps missing braces in buff-ini.mkiv?

2016-09-06 Thread Henri Menke 
On 09/06/2016 10:36 AM, Hans Hagen wrote:
> On 9/6/2016 9:05 AM, Henri Menke wrote:
>> Bump
>>
>> On 08/09/2016 10:54 AM, Henri Menke wrote:
>>> Dear list,
>>>
>>> it seems as if there are braces missing in the definition of \buff_save 
>>> around #2.
>>>
>>> \def\buff_save[#1][#2]%
>>>   {...
>>> {\setupcurrentsavebuffer[\c!list={#1},\c!file=#2]}%
>>>   ...}
>>>
>>> I think they are missing, because it makes the following work, even though 
>>> arguments and key-value arguments shouldn't be mixed up.
>>>
>>> \startbuffer[hash]
>>> foo
>>> \stopbuffer
>>> \savebuffer[hash][hello.txt,prefix=no]
>>> \starttext
>>> \stoptext
>>>
>>> I think you should either make a third argument for a key-value list or 
>>> just make the second argument the key-value list.  Then users could input 
>>> \savebuffer[hash][file=hello.txt,prefix=no].
> 
> the first argument can be a key/value list in which case the second one is 
> ignored
> 
> \savebuffer[list=hash,file=hello.txt,prefix=no]

I'd still recommend adding braces around this #2.  Imagine a user does this

\savebuffer[hash][my,file,name,with,commas.txt]

Cheers, Henri

> 
> Hans
> 
> -
>   Hans Hagen | PRAGMA ADE
>   Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
> ___
> 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
> ___

___
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
___

[NTG-context] Typset Text on odd pages only

2016-09-06 Thread Michael Eidenbenz 
Hello,

I'm looking for a way to produce a doublesided document with text on the odd 
pages only and floats on the even pages. 

Can somebody guide me in the right direction?

Will something like \doifoddpageelse {typsettext} {\page} work? 

Thanks Michael
___
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
___

Re: [NTG-context] Perhaps missing braces in buff-ini.mkiv?

2016-09-06 Thread Hans Hagen 

On 9/6/2016 9:05 AM, Henri Menke wrote:

Bump

On 08/09/2016 10:54 AM, Henri Menke wrote:

Dear list,

it seems as if there are braces missing in the definition of \buff_save around 
#2.

\def\buff_save[#1][#2]%
  {...
{\setupcurrentsavebuffer[\c!list={#1},\c!file=#2]}%
  ...}

I think they are missing, because it makes the following work, even though 
arguments and key-value arguments shouldn't be mixed up.

\startbuffer[hash]
foo
\stopbuffer
\savebuffer[hash][hello.txt,prefix=no]
\starttext
\stoptext

I think you should either make a third argument for a key-value list or just 
make the second argument the key-value list.  Then users could input 
\savebuffer[hash][file=hello.txt,prefix=no].


the first argument can be a key/value list in which case the second one 
is ignored


\savebuffer[list=hash,file=hello.txt,prefix=no]

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
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
___

Re: [NTG-context] insert pagebreak in toc (MkIV)

2016-09-06 Thread Robert Blackstone 

On 6 Sep 2016, at 09:06 ,  Robert Blackstone 
> To: ntg-context@ntg.nl
> 
> On 5 Sep 2016, at 11:06 ,  Hans Hagen  wrote
>> 
>> On 9/5/2016 9:06 AM, Robert Blackstone wrote:
>>> 
>>> I need a pagebreak in the ToC to avoid a widow.
>>> So far I used the method given in sept 2010 in 
>>> https://mailman.ntg.nl/pipermail/ntg-context/2010/052739.html, and
>>> still on http://wiki.contextgarden.net/Table_of_Contents#Forced_Page_Break, 
>>>  but
>>> it does not seem to work anymore.
>>> 
>>> MWE (from the first-mentioned site):
>>> %%%
>>> 
>>> \definelistextra[page][before=\page,after=\page]
>>> 
>>> \starttext
>>> 
>>>\placelist[chapter,section][criterium=text,extras={1.1=page}]
>>> 
>>>\chapter{x1}
>>>\section{xx1}
>>>\section{xx2}
>>>\chapter{y2}
>>>\section{yy1}
>>>\section{yy2}
>>> 
>>> \stoptext
>>> 
>>> %
>>> Compiled with a recent mkiv, from between sept 2015 till july 2016, the
>>> result shows no page break in the ToC.
>>> What can be done about this?
>> 
>> \showinjector
>> 
>> \setinjector[register][3][\column]
>> \setinjector[list][2][{\blank[3*big]}]
>> 
>> \starttext
>>\placelist[section][criterium=text]
>>\blank[3*big]
>>\placeregister[index][criterium=text]
>>\page
>>\startsection[title=Alpha] first  \index{first}  \stopsection
>>\startsection[title=Beta]  second \index{second} \stopsection
>>\startsection[title=Gamma] third  \index{third}  \stopsection
>>\startsection[title=Delta] fourth \index{fourth} \stopsection
>> \stoptext
> 
> Thanks Hans, for your quick reaction.
> 
> Maybe my question was not clear enough but in any case your remedy does not 
> help me.
> .. etc.

Dear Hans, 
My apologies. Your remedy does help. Initially I just didn’t understand what to 
do with this injector.

Best regards,
Robert Blackstone


> 
> 
> 
> 
> 
> 
> --
> 
> Message: 2
> Date: Mon, 5 Sep 2016 16:33:53 +0200
> From: Pablo Rodriguez 
> To: mailing list for ConTeXt users 
> Subject: Re: [NTG-context] bug in latest beta?
> Message-ID: <58e9fb16-dade-5cb0-3c0c-c2cc572d9...@gmx.es>
> Content-Type: text/plain; charset=utf-8
> 
> On 09/05/2016 10:39 AM, Akira Kakuto wrote:
>>> the following sample gives a Lua error with latest beta (2016.09.04 13:46):
>> 
>> Compilation is fine in the latest luatex 0.98.4 with
>> mtx-context | current version: 2016.09.04 13:46.
>> 
> 
> Hi Akira,
> 
> it seems that luatex-0.98.4 has been released for Windows today.
> 
> I will wait for the release in the Linux 32bit platform.
> 
> Luigi, would it be possible that all platforms have the latest LuaTeX
> version included?
> 
> Many thanks for your help,
> 
> 
> Pablo
> -- 
> http://www.ousia.tk
> 
> 
> --
> 
> Message: 3
> Date: Mon, 5 Sep 2016 16:44:16 +0200
> From: luigi scarso 
> To: mailing list for ConTeXt users 
> Subject: Re: [NTG-context] bug in latest beta?
> Message-ID:
>

Re: [NTG-context] Enumeration: chapter in counter, problem next to placefigure, and documentation issues

2016-09-06 Thread Florian Leupold 

> On 06.09.16, at 02:55, Aditya Mahajan  wrote:
> 
> On Mon, 5 Sep 2016, Florian Leupold wrote:
> 
>> One problem, however, persists: The theorem environment gets misplaced when 
>> a figure is placed to its left:
>> 
>> \setupexternalfigures[location=default]
>> \setupenumerations[
>>  alternative=left,
>>  text=Theorem,
>>  title=no,
>>  stopper={:},
>>  distance=0ex,
>>  width=fit,
>>  right={~},
>>  style=normal,
>>  hang=fit]
> 
> I am not sure what visual layout you want, but how about using:
> 
> \setupenumerations[
>alternative=serried,
>text=Theorem,
>title=no,
>stopper={:},
>distance=0ex,
>width=fit,
>right={~},
>style=normal,
>  ]
> \defineenumeration[theorem]
> 
> Aditya
> 
> ___
> 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
> ___

Dear Aditya,

thanks, that is indeed what I wanted to achieve. I don’t know why I got hung up 
with “alternative=left”.

Best,
Florian


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
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
___

Re: [NTG-context] Perhaps missing braces in buff-ini.mkiv?

2016-09-06 Thread Henri Menke 
Bump

On 08/09/2016 10:54 AM, Henri Menke wrote:
> Dear list,
> 
> it seems as if there are braces missing in the definition of \buff_save 
> around #2.
> 
> \def\buff_save[#1][#2]%
>   {...
> {\setupcurrentsavebuffer[\c!list={#1},\c!file=#2]}%
>   ...}
> 
> I think they are missing, because it makes the following work, even though 
> arguments and key-value arguments shouldn't be mixed up.
> 
> \startbuffer[hash]
> foo
> \stopbuffer
> \savebuffer[hash][hello.txt,prefix=no]
> \starttext
> \stoptext
> 
> I think you should either make a third argument for a key-value list or just 
> make the second argument the key-value list.  Then users could input 
> \savebuffer[hash][file=hello.txt,prefix=no].
> 
> Cheers, Henri
> 

___
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
___