From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Perhaps missing braces in buff-ini.mkiv?
Date: Tue, 6 Sep 2016 22:03:15 +0200 [thread overview]
Message-ID: <448e4a90-630f-db9e-8a37-ee19bad2d828@wxs.nl> (raw)
In-Reply-To: <cd6303f4-6a2c-a927-bac1-9a7316d83ac9@gmail.com>
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
___________________________________________________________________________________
prev parent reply other threads:[~2016-09-06 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 8:54 Henri Menke
2016-09-06 7:05 ` Henri Menke
2016-09-06 8:36 ` Hans Hagen
2016-09-06 18:45 ` Henri Menke
2016-09-06 20:03 ` Hans Hagen [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=448e4a90-630f-db9e-8a37-ee19bad2d828@wxs.nl \
--to=pragma@wxs.nl \
--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).